Software Testing and Quality Control

In French, 'Entretien' means 'Maintenance' in the context of property or equipment upkeep. This differs from 'Testing' which is 'Essai', and 'Requirements' which is 'Exigences'.

In French, 'Essai' translates to 'Testing' or 'Trial'. This is the standard term for software or quality assurance testing. Support (Support), Development (Développement), and Maintenance (Entretien) are different SDLC phases.

In French, 'Exigences' translates to 'Requirements' or specifications. Urgency is 'Urgence', Testing is 'Essai', and Deadline is 'Date limite' - all related project management concepts but distinct terms.

All the listed items (taking tests at the same time, using Google, having handouts) can be helpful during exit tests. The question asks for the most helpful item, and All the above correctly indicates that all these resources can assist students.

Usability testing requires human observation and subjective assessment of user experience, making it difficult to automate reliably. Load testing, regression testing, and security testing can all be effectively automated using software tools and scripts.

FMEA stands for Failure Mode and Effects Analysis, a systematic method for identifying potential failures in a process, product, or system, and assessing their impact. It's a proactive risk management tool used in engineering and quality management.

This statement is True and represents a fundamental principle of software testing articulated by Edsger Dijkstra: 'Program testing can be used to show the presence of bugs, but never to show their absence.' Testing can only demonstrate that defects exist under certain conditions, not prove the software is completely error-free. Absolute confidence in software correctness requires formal mathematical verification methods beyond testing.

Preventive testing involves verifying documents, designs, and code at each stage of development to prevent errors from entering the system. Unlike detective testing which finds existing defects, preventive testing aims to stop defects from being introduced in the first place through reviews, inspections, and validation at every phase of the development lifecycle.

Software testing validates and verifies that software meets business and technical requirements, works as expected, and can be implemented with the required characteristics. These are the three fundamental objectives of testing: requirement validation, functional verification, and implementation characteristics assessment. Testing provides confidence that the software is fit for its intended purpose.

Specification-based testing (also called black-box testing) focuses on verifying software functionality against requirements and specifications without examining internal code structure. It tests what the system should do based on documented requirements, user needs, and functional specifications. This contrasts with structure-based (white-box) testing which examines internal implementation.

This statement is True. As established by Edsger Dijkstra's famous principle, software testing can demonstrate the presence of bugs but can never prove their absence. Testing is a sampling technique that shows defects exist under specific test conditions, but provides no guarantee about untested scenarios. Complete confidence in error-free software requires mathematical proof techniques beyond empirical testing.

CSV (Comma Separated Values) is the standard format for bulk uploads in most database and portal systems because it's lightweight, universally compatible, and easy to generate from spreadsheets. While Excel can save as CSV, the native .xls/.xlsx format is not typically accepted for bulk uploads.

The maximum number of Test Cases that can be uploaded in a single file through the Bulk Upload tab is 499. Options B (500), C (501), and D (498) are incorrect as they don't match the system's upload limit.

After Test Cases are inserted into the database, ETP values can be modified either manually (one row at a time) OR through the Test Case Bulk Update Tab. Option B (Bulk Upload) is typically for initial uploads, not updates. Option D is incomplete, and options A, B, C alone are each insufficient.

The 'No. of similar Test Cases' field cannot be 0 because if a test case has no similar cases, this field should not be used or should be left blank/null rather than containing zero. Options B (1), C (10), and D (100) are all valid positive values that represent counts of similar test cases.