Test Plan :

- A test plan can be defined as a document describing the scope, approach, resources, and
schedule of intended testing activities. It identifies test items, the features to be tested, the
testing tasks, who will do each task, and any risks requiring contingency planning.
- a test plan gives detailed testing information regarding an upcoming testing effort,
including
Scope of testing
Schedule
est !eliverables
"elease #riteria
"isks and #ontingencies
- 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 testing plan is a methodological and systematic approach to testing a system such as a
machine or software. It can be effective in finding errors and flaws in a system. In order to
find relevant results, the plan typically contains e$periments with a range of operations and
values, including an understanding of what the eventual workflow will be.
- est plan is a document which includes, introduction, assumptions, list of test cases, list of
features to be tested, approach, deliverables, resources, risks and scheduling.
Scenario Testing %
- Scenario testing is done to make sure that the end to end functioning of software is working
fine, or all the business process flows of the software are working fine.
- In scenario testing the testers put themselves in the end users shoes and figure out the the
real world scenarios or use cases which can be performed on the software by the end user.
- Scenario testing helps testers to e$plore how the software will work in the hands of an end
user.
- Since scenario testing tests the business flow of the software, it helps in finding lot of
defects which cannot be found with other types of testing.
- Scenario testing is done by creating test scenarios which replicate the end users usage.
- A test scenario can be a independent test case or a series of test cases that follow each other.
est scenario is &ust a story which e$plains the usage of the software by any end user.
Sample Test Scenario Document
Sce.Id Requirement Name Test Scenario Test Cases
' (ogin )* #ancel
'+,erify )* with
,alid data
-+,erify )* with
Invalid data
.+,erify #ancel
- Add Insert #ancel
'+,erify Insert with
valid data
-+ ,erify Insert with
Invalid !ata
. Search Search #ancel
'+,erify Search with
,alid !ata
-+,erify Search with
invalid !ata
.+,erify #ancel
/ 0dit
1pdate #ancel
2ome
'+,erify 1pdate
with valid data
-+verify 1pdate with
Invalid !ata
.+,erify 1pdate
with missing
mandatory fields
/+,erify #ancel
3+,erify 2ome
3 !elete !elete '+,erify !elete
4 #ancel #ancel '+,erify #ancel
5 2ome 2ome '+,erify 2ome
6 (ogout (ogout '+,erify (ogout
Entry Criteria for Software Testing :
- entry criteria is a set of conditions that permits a task to perform, or in absence of any
among these condition will not allow to perform that task is taken as the 0ntry #riteria of
that task.
7or 0$ample
If you have to write est cases, what you will require to do that,
- he requirement 87unctional 9:usiness+ doc,
- #omplete understanding of the flow,
- he test case format9ool that is used in your organi;ation and many
more
Eit Criteria for Software Testing :
- !eadlines 8release deadlines, testing deadlines, etc.+
- est cases completed with certain percentage passed
- est budget depleted
- #overage of code9functionality9requirements reaches a specified point
- All defects are fi$ed or closed
-#losure reports are singed off
-All the test cases have been e$ecuted and passed
-:eta or alpha testing period ends
-:udget allocated for testing is e$hausted
-he risk in the pro&ect is under acceptable limit.
Test Cases can !e used for Com!o "o #alidation
- select the list bo$ of the combo
- See whether the list bo$ elements are sorted
alphabetically.
- If you enter a letter, only the list bo$ elements with
- the letter typed should be highlighted.
- the keyboard up and down should be navigable.
- If there are &ust 6 elements in the list bo$, scroll for
the combo not necessary.
- ry to type something in the combo bo$ - It should not
accept any value in the combo bo$.
Different ways to test t$e %ogin &unction
1) Correct com!ination of username and password
2) Incorrect com!ination of username en password
3) Correct username and empty password
4) Correct password and empty username
5) Correct login' logout and go !ac( wit$ t$e !rowser !utton
6) )o directly to a page wit$out use of t$e login function
7) C$ec( t$e sustaina!ility of t$e session
8) C$ec( if t$e login function is already *TTPS
9) C$ange t$e ID into an ID of anot$er account
10) Copy t$e ID and past t$is in anot$er !rowser
11) Delete t$e ID and continue !rowsing
Different ways to test Password &ield :
1) <assword typed should be in encrypted format
2) Inserting of password by copy the encrypted format and pasting it should not be allowed
3) #heck for minimum and ma$imum character value.should display a tooltip for minimum and
#haracter should not be inserted if it e$ceeds the limit
4) <assword cannot be blank