Computer Knowledge

Software Testing and Quality Control

2,292 Questions

Software testing and quality control questions cover testing methodologies, unit testing, and defect management. These concepts are crucial for the computer knowledge sections of competitive exams. Practice these questions to understand verification and validation processes thoroughly.

Quality control typesUnit testing purposeSoftware vulnerability testingTest planning tasksLoop testing criteriaTest harness functions

Software Testing and Quality Control Questions

Multiple choice technology testing

Error Guessing can be used to supplement?

  1. Only with Acceptance Testing

  2. Formal Testing Methods

  3. Only with Systems Testing

  4. Informal Test Design Techniques
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Error Guessing is an informal test design technique where testers use their experience to guess where defects might exist. It supplements formal testing methods (like equivalence partitioning or boundary value analysis) by providing additional test ideas based on intuition and past defect patterns. It is not limited to any specific testing level or phase.

Multiple choice technology testing

Deviating from the specified behaviour that is visible to end users is called?

  1. A fault

  2. A failure

  3. A defect

  4. An error
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

A failure is the deviation of the component or system from its expected delivery, service, or result. It occurs when a defect (fault) executes during runtime and causes the actual behavior to differ from the specified/expected behavior visible to end users. Error is a human mistake, defect is the manifestation in code, failure is the observable incorrect behavior.

Multiple choice technology testing

When should you stop testing?

  1. When the allocated time has run out

  2. When all planned tests have been executed

  3. It is dependant on the risks for the item under test

  4. When there are no more faults
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Testing stops based on risk criteria and completion criteria, not arbitrary constraints like time or executing all planned tests. The decision depends on the acceptable level of residual risk for the system under test. Even after planned tests complete, you may continue testing if residual risk is unacceptable, or stop early if risk is sufficiently mitigated.

Multiple choice technology testing

Why isn’t Exhaustive Testing commonly used?

  1. There simply aren’t enough test cases

  2. Most Tester’s don’t like it

  3. There simply isn’t enough time

  4. It can be tiring
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Exhaustive testing (testing all possible input combinations and preconditions) is impractical because the number of possible test cases is infinite or astronomically large. With even simple inputs, the combinatorial explosion makes it impossible to test everything within reasonable timeframes. This is why we use risk-based testing, sampling, and test design techniques.

Multiple choice technology embedded technologies

Debug support mechanism is used for

  1. Fault finding only

  2. Fault Corrections only

  3. Fault finding and fault corrections

  4. Load shifting
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Debug support mechanisms serve dual purposes: identifying problems (fault finding) and implementing corrections (fault corrections). Options A and B are incomplete, each describing only one half of the debugging process. Option D (load shifting) is unrelated to debugging functionality.

Multiple choice technology embedded technologies

Debug support mechanish is used for :

  1. Fault finding only

  2. Fault corrections only

  3. Fault finding and fault corrections

  4. Load sharing
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Debug support mechanisms are designed to assist developers in both identifying and fixing faults in software systems. The process involves first detecting the issue (fault finding) and then implementing a solution (fault correction). Options A and B are incomplete as they only cover one aspect of the debugging process, while option D (load sharing) is unrelated to debugging functionality.

Multiple choice technology testing

Testing to determine if a new software version is performing well enough to accept it for a major testing effort.Identify the type of testing

  1. Basic Testing

  2. Acceptance testing

  3. Usability testing

  4. Sanity Testing
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Sanity testing is performed to determine if a new software version is stable enough to be accepted for major testing efforts. It's a preliminary test to ensure basic functionality works before committing to more comprehensive testing. Basic Testing isn't a standard term, Acceptance testing comes later, and Usability testing focuses on user experience.

Multiple choice technology testing

Testing how well software performs in a particular hardware/software/operating system/network environment and different combinations of above. Identify the type of testing

  1. Comparision Testing

  2. Compatibility Testing

  3. Beta testing

  4. Environment testing
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Compatibility testing evaluates how well software performs across different hardware, software, operating systems, and network environments, including various combinations. This matches the description exactly. Comparison testing compares different versions, Beta testing is done by users, and Environment testing isn't a standard term.

Multiple choice technology testing

Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.Identify the type of testing

  1. Alpha testing

  2. Beta testing

  3. User Acceptance testing

  4. System tetsing
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Beta testing is typically done by end-users or external testers and is the final testing phase before commercial release. Alpha testing is internal, User Acceptance Testing is done by stakeholders before beta, and System testing is more comprehensive. Note: There's a typo in option D ('tetsing' instead of 'testing').

Multiple choice technology testing

Testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.Identify the type of testing

  1. Beta Testing

  2. User acceptance testing

  3. End-to End testing

  4. System testing
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

End-to-end testing validates the entire application flow in a real-world environment, including interactions with databases, networks, hardware, and other systems. Beta testing is user testing before release. User acceptance testing (UAT) is done by end users to verify requirements. System testing tests the integrated system but not necessarily with real-world external dependencies.

Multiple choice technology testing

System is made to perform beyond its specifications to check how and when it fails.Identify the type of testing

  1. Load testing

  2. Stress testing

  3. Performance testing

  4. Usability testing
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Stress testing pushes a system beyond its specified limits to see when and how it fails. Load testing tests system performance under expected load. Performance testing measures system responsiveness. Usability testing evaluates user experience and interface usability.

Multiple choice technology testing

Why must QA log off when deployment is in progress?

  1. Impact software upgrades deployment time

  2. Impact software upgrades deployment time & no longer testing current code version

  3. May no longer be testing correct version of code

  4. Lunch break
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

To answer this question, the user needs to understand the purpose of QA in software development and the importance of logging off during deployment.

Option A is not correct because QA's log off does not impact software upgrades deployment time.

Option B is the correct answer. QA should log off during deployment because the deployment process involves updating the software to a new version. If QA is still testing the current code version while the deployment is in progress, they may inadvertently test the wrong version of the code, leading to inaccurate results and errors.

Option C is also correct and provides a more specific explanation of why QA should log off during deployment.

Option D is not correct because lunch breaks are unrelated to deployment or QA.

Therefore, the correct answer is:

The Answer is: B. Impact software upgrades deployment time & no longer testing current code version.