Priority: Severity: M A N U A L T E S T I N G C H E A T S H E E T - R A J

Testing: software testing is an activity to check

The Importance of the The seriousness of the defect whether the actual results match the expected
defect to be resolved with in terms of functionality. results and to ensure that the software system is
SDLC: Software Development Life Cycle defines the steps/stages/phases in the building defect free
respect to the customer.
of software.
Retesting: Regression Testing: Quality: The degree to which a component, system
Information gathering -> Analysis -> Design -> Coding -> Testing ->Maintenance or process meets specified requirements and/or
Retesting is the act of The Re-Execution of selected
repeating a test to verify that tests on modified build to user/customer needs and expectations
a found defect has been estimate Completeness and Waterfall Model is suitable when the customer requirements are clear and complete DRE: Defect Removal Efficiency
correctly fixed correctness of modification is Prototype Model is suitable when the customer requirements are unclear and confusing DRE = A / A + B
called Regression Testing. RAD Model is suitable when the customer requirements are clear but not complete, A -> Bugs found during testing at development
because client is giving requirements in installment basis. B -> Bugs found at the client
White Box Testing Black box Testing
Spiral Model is suitable when the customer requirements are clear and complete but Defect Density: Defect Density is the number of
1)Black Box Testing is a 1)White Box Testing is a
enhancing in future confirmed defects detected in software during a
software testing method in software testing method in
which the internal structure which the internal structure Advantages Disadvantages defined period of development divided by the size
of the item being tested is of the item being tested is Waterfall Model: of the software (Size  Functional points and LOC)
NOT known to the tester. known to the tester. 1) It is a linear model, and follows a 1) If the customer is ambiguous about Defect age: Defect Age is the difference in time
2)Programming Knowledge 2)Programming Knowledge proper sequence and order his needs, the design process can go between detected on and resolved on.
not required. Required. 2) Documentation is produced at every horribly wrong. This factor is further RTM: Traceability matrix is nothing but mapping
3)Mainly applicable to higher 3)Mainly applicable to lower stage, it is easy to track down mistakes, highlighted by the fact that if some between Requirements and test cases to ensure
levels of testing: levels of testing: deficiencies and any other problems mistake is made in a certain stage that all requirements covered.
1)Acceptance Testing 1)Unit Testing that may arise and is not detected or tracked; all Test Cases for Washing Machine:
2)System Testing 2)Integration Testing 3) The cost of resources at each stage get the subsequent steps will go wrong. 1)Verify Power supply.
minimized due to the linear sequencing Therefore the need for testing is very 2)Verify door open.
QA QC as well intense 3)Verify water filling with detergent
1)It is process oriented 1)It is product oriented. Spiral Model 4)Verify cloths filling.
2)It involve in entire process of 2)Work to examine the quality 1) High amount of risk analysis 1) Can be a costly model to use. 5)Verify door close.
software development. of product. 2) Good for large and mission-critical 2) Risk analysis requires highly specific 6)Verify door close with cloths overflow.
3)It is prevention oriented. 3)It is detection oriented. projects. expertise. 7)Verify washing settings selection.
3) Software is produced early in the 3) Project’s success is highly dependent 8)Verify washing operation.
software life cycle. on the risk analysis phase. 9)Verify washing operation with lack of water.
Unit Testing: The testing of individual software components
RAD Model: 10) Verify washing operation with cloths overload.
Integration Testing: Testing performed to expose defects in the
1) It increases speed of developing 1) Unknown cost of product. 11) Verify washing operation with improper settings.
interfaces and in the interactions between integrated
components or systems. software. 2) Difficult to commit the time required 12) Verify washing operation with machinery
System Testing: The process of testing an integrated system to 2) Re-usability of components helps to for success of the RAD process. problem.
verify that it meets specified requirements. speed up development. 3) Short iteration may not add enough 13) Verify washing operation due to water leakage
Monkey Testing: Due to lack of time, the testing team through door.
3) It increases the quality. functionality, leading to significant
concentrates on some of the main activities in the software 14) Verify washing operation due to door open in
4) Some systems also deliver advantages delays in final iterations. the middle of the process.
build for testing. This style of testing is known as Monkey testing
of interoperability, extensibility, and 4) Success depends on the extremely 15)
or Chimpanzee testing or Gorilla testing. Test Verify washing
Engineer operation with improper power.
Responsibilities:
Acceptance Testing: Formal testing with respect to user needs, portability. high technical skills of the developers. 1)Review of software requirements
requirements, and business processes conducted to Prototype Model 2)Preparation of test cases
determine whether or not a system satisfies the acceptance 1) Helps in reducing risk associated with 5) This model is time consuming and 3)Execution of tests
criteria and to enable the user, customers or other authorized the project. expensive. Because if the user is not 4)Reporting of defects
entity to determine whether or not to accept the system. 2) There is a great involvement of user in satisfied by the developed prototype 5)Preparation of test reports
s/w development. then a new prototype is developed. Integration testing Approaches:
Testing is enough when the 90% of requirements are covered, This process goes on until a perfect 1)Top-Down Approach: Top Down is an approach
Maximum defects are rectified except (some) low level V-Model prototype is developed. to Integration Testing where top level units are
defects are not covered, customer satisfy that project and 1) Simple and easy to use. 1) Very rigid, like the waterfall model. tested first and lower level units are tested step by
time is less, then we are closing the testing. 2) Each phase has specific deliverables. 2) Little flexibility and adjusting scope is step after that. This approach is taken when top
3) Higher chance of success over the difficult and expensive. down development approach is followed. Test
1) Error: programmatically mistake leads to error. 3) Software is developed during the
waterfall model due to the Stubs are needed to simulate lower level units
2) Bug: Deviation from the expected result. implementation phase, so no early
development of test plans early on which may not be available during the initial
3) Defect: Problem in algorithm leads to failure. prototypes of the software are
during the life cycle. phases.
4) Failure: Result of any of the above. produced.
4) Works well for small projects where 2)Bottom-Up Approach: Bottom Up is an approach
requirements are easily understood. 4) Model doesn’t provide a clear path to Integration Testing where bottom level units are
for problems found during testing. tested first and upper level units step by step after
Software Testing Life Cycle
Bug Life Cycle: Bug Status Cycle that. This approach is taken when bottom up
Test Initiation
Detect defect New development approach is followed. Test Drivers
Test Planning
Report defect Assigned are needed to simulate higher level units which
Test Design
Resolve defect Open/Rejected/Differed may not be available during the initial phases.
Test Execution
Re-test defect Fixed 3)Sandwich Approach: Sandwich/Hybrid is an
Test Closure
Close defect Closed approach to Integration Testing which is a
UAT
Reopen combination of Top Down and Bottom Up
Signoff
approaches