Manual Testing:

1. What is Test Plan?

Test Plan is a document that describes how the Testing will be conducted.
Test Plan is a planning document which has information about the scope,
resources, duration, test coverage and other details.
It is also be described as a detail of how the testing will proceed, who will do the testing, what
will be tested, in how much time the test will take place, and to what quality level the test will
be performed.
A Test plan is a document that describes the objectives, scope, approach and focus of a software testing effort.
Test plan can be written during the requirement analysis phase.
A Project can have only one(1) Test Plan.
Test Plan also describes the scope, approach, resources, and schedule of testing. It identifies
test items, features to be tested, testing tasks, and any risks requiring contingency panning.

When Test Plan comes into picture
After completion of Test Process finalization, for corresponding project, Author(Test Manager or Test
Lead) prepares the document. Test plan is prepared based on the BRS and SRS documents.

In software testing, a test plan gives detailed testing information regarding an upcoming
testing effort, including
Scope of testing
Schedule
Test Deliverables
Release Criteria
Risks and Contingencies


2. What are the Contents of a Test Plan?
Content of Test Plan:
a) Introduction
b) Application Details
c) Testing Scope (IN/OUT)
d) Roles and Responsibility
e) Supporting Documents
f) Test Strategies
g) Test Schedule/ Testing Cycle
h) Dependencies
i) Test Environment/ Test Data
j) Enter and Exit Criteria
k) Glossary.



3. What are Test Cases?

A test case is a document that describes an input, action, or event and an expected
response, to determine if a feature of an application is working correctly. A test
case should contain particulars such as test case identifier, test case name,
objective, test conditions/setup, input data requirements, steps, and expected
results.

Test case document has information about the test data to be used.

4. Why we write test cases?
The basic objective of writing test cases is to validate the testing coverage
of the application. If you are working in any CMMi company then you will
strictly follow test cases standards. So writing test cases brings some sort of
standardization and minimizes the ad-hoc approach in testing.

5. How to write Test Cases?
unique-test-case-id: Test Case Title
Purpose: Short sentence or two about the aspect of the system is being tested. If this
gets too long, break the test case up or put more information into the feature
descriptions.
Prereq: Assumptions that must be met before the test case can be run. E.g., "logged
in", "guest login allowed", "user testuser exists".
Test Data: List of variables and their possible values used in the test case. You can list
specific values or describe value ranges. The test case should be performed
once for each combination of values. These values are written in set notation,
one per line. E.g.:
loginID = {Valid loginID, invalid loginID, valid email, invalid email,
empty}
password = {valid, invalid, empty}
Steps: Steps to carry out the test. See step formating rules below.
1. visit LoginPage
2. enter userID
3. enter password
4. click login
5. see the terms of use page
6. click agree radio button at page bottom
7. click submit button
8. see PersonalPage
9. verify that welcome message is correct username



6. How to execute Testing?