this ppt consists of basic information about testing and test cases.

2.  Miscommunication or No communication(That is,we
are not clear about what an application should do or
shouldn’t do).
 Time pressure(Time scheduling).
 Changing Requirements.
 Software Complexity(without experience its tough to
do the tough application).
 Programming Mistakes.

3. To find and correct defects.
To check whether the Client/User needs are
satisfied.
To avoid user detecting problems.
Finally,to Provide a Quality product .

4.  Uncover as many as errors as possible in a
product.
 Demonstrate a given software product matching
its requirement specification.
 Validate the quality of the software testing using
the minimum cost and efforts.
 Generate high quality test cases,perform
effective tests,and issue correct and helpful
problem reports.

5. Error:It is a Human action that produces the
incorrect result that produces a fault.
Bug:The presence of error at the time of
execution of the software.
Fault:State of software caused by an error.
Failure:Deviation of the software from its
expected result.Its an event.

6.  A test case has an input, an action and an
expected result.
 Also, a test case is a set of what-if questions.
 Test cases must exercise every feature of the
application to prevent defects from being
released.
 Each test case needs to contain a set of test
steps of a feature or function.
 A test case can have information that includes
the test case name, goal, environment, steps to
take, input and expected results.

7.  At the end of the test the expected results
are compared to actual results to determine if
the application is working as it should.
A successful test case is the one that detects
an undiscovered error.
Hopefully, serious defects that crash the
system are found before application is
released to the customer.

8. The following are the types of test cases.
Functional
Negative
Error
Logical test cases
Physical test cases
UI test cases.

10. Can be difficult at initial stage.
Can test if a component conforms to
Specification-BLACK BOXTESTING.
Can test if a component conforms to Design-
WHITE BOXTESTING.
Testing can not prove correctness as not all the
Execution paths can be tested.

12. Expected Result :The expected outcome of
the test case.
Actual Result :What we have received during
the execution of the test case.
If Expected result is equal to Actual result,
then the test is pass otherwise it is fail.

13. Testing is part of software quality assurance.
Quality Assurance: Process of monitoring and
improving the whole software development
process.
Verification:Are we building right software?
Validation: Did we build the software right?

14.  First analyze, what are the features and
services our test attempts to cover.
 Test object’s interactions and the messages
sent among them.
 Boundary conditions need to be test.
 Specify the methods which are included to
testing.
 Test the normal use of the object’s methods.
 Test the abnormal use of the object’s methods,
but the abnormal to be reasonable.

15.  Test the abnormal use of the object’s
methods, but the abnormal to be
unreasonable.
 Document the cases, when the revisions
have been made.
 If our test case is based on use case then we
can refer it with use-case name.
 Assess the internal quality, reusability and
extendability of software.