QA Testing Questions

Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Priority: concern with application from the business point of view. It answers  How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity: concern with functionality of application. It deals with the impact of the bug on the application.

Automated testing cannot replace manual testing because of following reason:

- Automated testing cannot replace the analytical skills required to conduct testing. It can only enhance or supplement manual testing,

- Through manual testing, information can be gathered about the application, and real-time decisions can be made about how to enhance a test that would be too difficult to program into an automated script.

- We need a manual tester to analyze and maintain the automated scripts after they can run.

Time Estimation method for Testing Process:

Step 1 : count number of use cases (NUC) of system 

Step 2 : Set Avg. Time Test Cases(ATTC) as per test plan 

Step 3 : Estimate total number of test cases (NTC) 

Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case 

Step 4 : Set Avg. Execution Time (AET) per a test case 

Step 5 : Calculate Total Execution Time (TET) 

TET = Total number of test cases * AET 

Step 6 : Calculate Test Case Creation Time (TCCT)

usually we will take 1.5 times of TET as TCCT

TCCT = 1.5 * TET

Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting

usually we take 0.5 times of TET

RTCE = 0.5 * TET

Step 8 : Set Report generation Time (RGT

usually we take 0.2 times of TET

RGT = 0.2 * TET

Step 9 : Set Test Environment Setup Time (TEST)

it also depends on test plan

Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.

Similar to system testing, the *macro* end of the test scale is testing a complete application in a situation that mimics real world use, such as interacting with a database, using network communication, or interacting with other hardware, application, or system.

For web application we perform following time of test:

1. Functionality Testing.

2. Usability Testing.

3. Navigation Testing.

4. Configuration and Compatibility testing.

5. Reliability and Availability Testing.

6. Performance Testing.

7. Load and Stress Testing.

8. Security Testing