Tag: testing

Questions Related to testing

  1. State transition testing, code testing, agile testing

  2. Equivalence partitioning, state transition testing, decision table testing

  3. System testing, acceptance testing, equivalence partitioning

  4. System integration testing, system testing, decision table testing


Correct Option: B
  1. The test object, the test material and the test environment

  2. The problem reports and the test material

  3. Only the test object. The test cases need to be adapted during agile testing

  4. The test object and the test material


Correct Option: A
  1. Because the tools for automated testing require too much effort for learning

  2. Because the maintenance of the test system is difficult

  3. Because the test robot tools are restricted in their ability to recognize outputs

  4. Because the test robot needs to be supported by a test management.


Correct Option: B
  1. A software development model that illustrates how testing activities integrate with software development phases

  2. A software life-cycle model that is not relevant for testing

  3. The official software development and testing life-cycle model of ISTQB

  4. A testing life cycle model including unit, integration, system and acceptance phases


Correct Option: A

Pick the best definition of quality

  1. Quality is job one

  2. Zero defects

  3. Conformance to requirements

  4. Work as designed


Correct Option: C
  1. 1000, 5000, 99999

  2. 9999, 50000, 100000

  3. 10000, 50000, 99999

  4. 10000, 99999

  5. 9999, 10000, 50000, 99999, 10000


Correct Option: C
Explanation:

To solve this question, the user needs to know about equivalence classes and boundary testing. Equivalence partitioning is a software testing technique that divides the input data of a software unit into different partitions of valid and invalid data. The purpose of this is to reduce the number of test cases needed to test the software while increasing the effectiveness of the tests. Boundary testing is a software testing technique that checks whether the input data to a software system is at its minimum or maximum limits.

In this question, the valid equivalence classes are numbers between 10000 and 99999 inclusive. The valid boundaries are 10000 and 99999.

Let's go through each option and see which inputs are a result of designing tests for only valid equivalence classes and valid boundaries:

A. 1000, 5000, 99999: Option A includes invalid equivalence classes and is not a result of designing tests for only valid equivalence classes.

B. 9999, 50000, 100000: Option B includes an invalid boundary (100000) and is not a result of designing tests for only valid boundaries.

C. 10000, 50000, 99999: Option C includes valid equivalence classes and valid boundaries. It includes the minimum and maximum values of the valid equivalence classes.

D. 10000, 99999: Option D includes valid boundaries but only one valid equivalence class. It does not include other valid equivalence classes between 10000 and 99999.

E. 9999, 10000, 50000, 99999, 10000: Option E includes invalid equivalence classes (9999 and 10000) and duplicate input (10000). It is not a result of designing tests for only valid equivalence classes and valid boundaries.

Therefore, the correct answer is:

The Answer is: C

  1. Post-release testing by end user representatives at the developer’s site.

  2. The first testing that is performed.

  3. Pre-release testing by end user representatives at the developer’s site.

  4. Pre-release testing by end user representatives at their sites.


Correct Option: C
  1. CASH

  2. V21

  3. SGI

  4. None Of the above

  5. All the above


Correct Option: B
  1. Handset Upgrade Payment

  2. Hardware Upgrade program

  3. Handset Upgrade Process

  4. Hardware Usage Payment


Correct Option: B
  1. Actions-> Credit Evaluation

  2. Page Options-> Payments

  3. Bills-> Payments

  4. Actions->One time payment


Correct Option: C