Escolar Documentos
Profissional Documentos
Cultura Documentos
15 Checking for the password when the user clicks on back once he
has logged in successfully to the site
Forgot Password
The following test cases can be used for the Forgot Password screen
The following assumptions are made
Forgot password has a question field and answer field an ok button and cancel button.
Change Password
The following test cases can be used for the Change Password screen
The following assumptions are made
Change password has three edit fields and ok and cancel button
Edit Fields are the following:
Old password
New password
Confirm new password
8 Enter incorrect old password with both the other two fields having
new password. Click on ok button
9 Enter old password and new password in new password field and
some other value in confirm password field. Click on ok button.
10 Enter the old password, and enter the new password in new
password field and confirm new password field. Click on Cancel
button
11 Enter the old password, and enter the new password in new
password field and confirm new password field. Click on Cancel
button
12 Enter old password and new password. Click on Cancel button.
13 Enter old password and confirm new password. Click on Cancel
button.
14 Enter new password and confirm new password . Click on Cancel
button.
15 Enter incorrect old password with both the other two fields having
new password. Click on Cancel button.
16 Enter old password and new password in new password field and
some other thing in confirm password field. Click on Cancel button.
Logout
The following test cases can be used for the Logout functionality
Required Output
The Username and Password fields should be cleared and the cursor should
wait in the Username filed
The application should not allow to access any screens other than the
allowed ones.
The application should behave same as Cancel button press
The password should not appear in clear in the URL when the user submits
the data
The user should not be able to copy the password and paste the same else
where example notepad
When the user clicks on Back button after successful login he should be
bought back to the login page with the password cleared
Forgot Password
n
Required Output
Change Password
en
Required Output
An error message should pop up saying that confirm password should not be
blank
An error message should pop up saying that new password should not be
blank
An error message should pop up saying that old password should not be
blank
An error message should pop up saying that old password is wrong.
An error message should pop up saying that the new password in confirm
password is different.
The old password should be retained.
When the user changes the password the mandatory length of the password
should be the same as and when we create the user
Logout
Required Output
For Windows
1 Check for the properties of the window
2 Check for the addressable nature of the data contained in the window
3 Check for the closing action of the window by all means like clicking on X
4 button
Click ononminimize
upper right corner,
button pressing
in the windowALT + F4, using menu close item,
5 using Control
Click on Box etc
Maximize button in the window
6 Click on Resize button in the window
7 Click on minimize and maximize buttons and see that repainting of the
windowwhether
8 Check happens allproperly
the pull down menus, toolbars, scrollbars, dialog boxes,
9 and
Havebuttons,
multipleicons and other
windows controls
and check for available
the namesand
on properly displayed
the individual window
10 Check for the active window when there are multiple windows
11 Check the updating of the windows when multi-tasking is going on.
12 Have multiple windows and click the mouse in some of the windows to
13 make it active
Click on the Move button and drag with the mouse
14 Click on the Move button and move using up arrow key
15 Click on the Move button and move using down arrow key
16 Click on the Move button and move using backward arrow key
17 Click on the Move button and move using forward arrow key
18 Check the look and feel of windows
19 Check the multiple instances of a window
20 Check when the screen is a model window user can access the other
screens in the application with out closing the model window
For Text Boxes
21 Check the height of the text boxes
22 Check the width of the text boxes
23 Observe the font and size of the values of the text boxes
24 Observe the alignment of the text boxes
25 Observe the non editable text boxes
26 Checking for the indentation of text (alpha Characters)
27 Checking for the indentation of text (Numeric Characters)
For Labels
56 Observe the height of the labels
57 Check the label description
58 Observe the positioning of labels
59 Observe the font and size of the labels
60 Check whether the label is enabled or disabled
61 Observe the alignment of the labels
Field Alignments
95 Check for the alignment of numeric fields
96 Check for the alignment of character fields
97 Check for the alignment of the controls
Hot Keys
134 Check for the alternative(hot-key) key for menu options
135 Check for the duplicate hot key's
Upload file
136 Check to upload a huge file through the upload screen
137 Check to upload files which contains the data in different format
Uploading files from shared network drives
Disturb the upload during a upload
Download file
Checking for the downloading of files to read-only path
Disturb the download during a download
General
The window can be moved, resized, minimized, maximized and scrolled both vertically and horizontally
All the data contained within the window are properly addressable with a mouse, function keys, directional arrows and keyboar
The window should close properly
Window should be minimized
Window should be maximized
Window should be resized
Window should properly regenerate when it is overwritten and then recalled
All the controls should be properly displayed on the window
Names on the all the windows should be properly displayed
Active window should be properly highlighted
When multi-tasking is used, all windows should be updated at appropriate times
There should not be any unexpected side effects on the other windows
Window should be moved in the mouse direction
Window should move in the upward direction
Window should move in the down direction
Window should move in the backward direction
Window should move in the forward direction
All windows should have a consistent look and feel.
This functionality is application specific
The user should not able to access the window with out closing the model window
The height of the text box should be consistent across the form
The width is accepting the maximum length of allowable characters (preferably enter all “W” to check for visibility(Capitals)). W
cannot be displayed,
The values should bescrolling is in
displayed allowed to view
consistent fontthe fullsize
and contents
across the form
The textbox should be properly aligned both horizontally and vertically
The textbox should be disabled when it is not editable
All the fields in the text box should be left aligned (should start from the left part of the edit box)
All the fields in the text box should be right aligned (should start from the right part of the edit box)
The height of the combo box should be consistent across the form
The width should be set to the maximum length of characters
The values should be displayed in consistent font and size across the form
The combo box should be disabled when it is not editable
The combo box should be properly aligned both horizontally and vertically
The values in the combo box should be sorted and verification should be done to ensure that all required items are present
It should be possible to use mouse to scroll down and select
It should be possible to use arrow keys to position the required item and select
It should accept any new entries (unless defined otherwise)
Data populated in the combo box and in the table should match
The data in the combo box should display in the sorted order
The combo box should display the values as per the entered key combinations
Combo box should display either the default value or blank
Ensure that the names are not abbreviations / cut short
When the field is a mandatory field the default value should always be pre-populated
The height of the List box should be consistent across the form
The width should be set to the maximum length of characters
The values in the list box should be displayed in consistent font and size across the form
The list box should be disabled when it is not editable
The list box should be properly aligned both horizontally and vertically
The values in the list box should be sorted and verification should be done to ensure that all required items are present
It should be possible use mouse to scroll down and select
It should be possible to use arrow keys to position the required item and select
It should not accept any new entries
If it’s multi line list box, vertical scrollbar and horizontal scrollbar should appear as appropriate
The list should select the matching initial character of the first word in the list entry, scrolling if necessary to keep the user’s sele
Data populated in the list box and in the table should match
The values in the list box should display in the sorted order
The list box should display the values as per the entered key combinations
List box should display either the default value or blank
Ensure that the names are not abbreviations / cut short
When the field is a mandatory field the default value should always be pre-populated
The user should be able to select only one item in the list of radio buttons either with mouse or by pressing space bar on the fie
The label description should be self explanatory and should be in proper case
The radio button should be aligned both vertically and horizontally
Able to toggle (check/uncheck) the check boxes either with the help of Mouse or by pressing space bar on the field
The label description should be self explanatory and should be in proper case
The check box should be aligned both vertically and horizontally
The title for the window should be meaningful and should be in proper case
The window close button should be present
The window minimize or maximize button should be present
The message in the window should be precise and the first character should be capitalized
Any command buttons should have short cut keys
Command buttons should function either clicking on it or with use of short cut keys or positioning the cursor on the command b
Enter key
The title for the Dialog box should be meaningful and should be in proper case
The dialog box close button should be present
The window minimize or maximize button should not be present
The message in the window should be precise and the first character should be capitalized
Any command buttons should have short cut keys
Command buttons should function either clicking on it or with use of short cut keys or positioning the cursor on the command b
Enter key
All the numeric fields should be right aligned by default. If decimals are used, decimal point should be displayed and generally
point should be
All character displayed
fields should be left aligned by default
All controls should be properly aligned. Both vertically as well as horizontally
The tab order should be in the order of the fields arranged, either from left to right or top to bottom or logical order
First enabled field on the screen should be getting the focus
On pressing shift + tab the cursor focus should be moving in the reverse order
On pressing tab on the last field, cursor should be positioning on the first field
Tab order should in sequence and go in sequence from top left to bottom right
Read only files should remove from the tab sequence
It should displays the progress of process in incremental steps as defined. The control should provide more visual feedback to
Once the process is over, the progress bar should disappear
Normally displayed in percentage of completion. It displays information, it is typically not interactive
There should be some static text or other information to help communicate the purpose
It should consists of bar that defines the extent or range of the adjustment and an indicator that show the current value for the c
User should be able to set or adjust the values on a continuous range, such as volume or brightness
User should able to move or drag slide by clicking through mouse
User should able to move or drag slide by arrow keys
There should be support for the tab key and access key for the static text field of the label
The length, height of the slide indicator and the slide bar component, should be unique across the form.
There should be constant increment of the slider, control should have tick marks on it
Label should be positioned either to the left of the slider or above it and aligned with the left edge of the slider
Use sentence-style capitalization for the slider label
Scroll arrow buttons should appear at each end of a scroll bar pointing in opposite directions away form the center of the scroll
When the user clicks a scroll arrow revealing information should moves in the direction of the arrow in appropriate increments.
Same scrolling increment should be maintained through out a window
When a window cannot be scrolled any further in a particular direction, scroll arrow in that direction should be disabled.
Window should continue its scrolling in the associated direction as long as the pointer remains over the arrow button.
The scroll box, should move along the scroll bar to indicate how for the visible portion is from the top (for vertical scroll bar)
horizontal
The size ofscroll bar) box can vary to reflect the diff between what is visible in the window and the entire contents of the file
the scroll
The user should be able to scroll a window by dragging the scroll box. It should update the view continuously as the user move
Scroll box should return to its original position.
Pressing arrow key, page up and page down keys should allow to scroll
A tree view control is a special list box control that displays a set of objects as an indented outline based on their logical hierarc
Different icons can be displayed when the user expands or collapses the item in the tree
Using arrow keys and text keys should be able to navigate through the control
It should expand the current branch and all its sub-branches
Assure that each menu command has an alternative(hot-key) key sequence which will invoke it where appropriate
Ensure that duplicate hot keys do not exist on each screen
The application should not hang and should display proper message
The application should allow to upload files with specified file format only.
The application should allow to upload files with specified file format only.
The application should throw a appropriate error message; and should not hang
Required Output
Should not allow the user to save. Should popup a information message box
Then the application has some back end process happening; the application should let the user known that its busy by displayi
When the there is any confirmation message like "Do you want to Save" the focus should always be on O.k.
Field Level Validation Test Cases
Scenario Scenario Description
No
For input box which accepts the numbers between the range x and y where x and y are any integers with x<y (Bou
50 Enter date greater than 29 for the month Feb and which is a leap year
51 Enter negative values in date, month and year columns
52 Enter the value zero in date, month or in year field
53 Leave either date or month or year blank and enter the other details
54 Enter date in mm/dd/yyyy format
55 If there are two date fields where in one is From date and the other is To
date, then try to enter From date greater than To date
56 If there are two date fields where in one is From date and the other is To
date, then try to enter From date less than or equal to To date
dation Test Cases
Required Output
y where x and y are any integers with x<y (Boundary Condition Testing)
Application specific
Job should be run at the first minute after the change in timing; Next
job should run on the scheduled time
It should not accept
It should not accept
It should not accept
It should not accept
It should accept the date
It should not accept
Required Output
The Login page of the application page should be displayed and the user
should not be allowed to access the application directly
The Login page should be displayed and user should not be allowed to view
the previous page
The password should be stored in the database in encrypted format
Appropriate error message should be displayed modification/deletion should
not be allowed
This should not be allowed or appropriate error message should be displayed
Database Test Cases
Required Output
s
ons
Guidelines for Performance Testing
Load/Volume testing
Typically, performance is stated as a measure of response time, throughput and/or resource usage, as measured under various c
Approach
- Determine the serviceability of the system for a volume of x concurrent users.
- Measure response times for users.
Steps
The following details need to be identified in the traversal document.
Idenify frequently used business scenarios,Risk scenarios with the helf of Business team. Identified scenario get approval fro
gather previous performance issues and design scenarios)
1. Virtual users estimation: Arrive at a maximum number of concurrent users hitting the system where the system response ti
threshold and the system is stable. This number would be the virtual user number and should be higher by a factor of x times th
2. Virtual users profiles and their distribution for client operations: Identify the transactions/scenarios performed by each us
Usage Profile is available with the Business side rather than the Development Side (Meet the right people)
3. Load simulation schedule: Design the schedule for concurrent user testing with a mix of users and the number of iterations
cyclically repeated starting with x number and than progressively approach y and measure the system response time. Define
intervals of the load.
Endurance testing
Objective
Validate systems behavior for Continuous Hours of Operation (CHO) for projected load conditions
Approach
- Endurance testing – check resource usage and release namely; CPU, Memory, Disk I/O and network (T
continuous hours of operation
- Determine the robustness - check for breakages in the web server, application server and data base serve
Steps
1. Arrive at a base line configuration of the web server and application server resources i.e. CPU, RAM an
and reliability test.
2. The test would be stopped when one of the components breaks. A root cause analysis is to be carried ou
described under the server side monitoring section.
Client side monitoring
- Failure rate -- web server responses/timeouts/exceptions and incomplete page downloads
- Response time degradation under peak load numbers (concurrent users)
Server side monitoring
- Collect CPU, Disk and Memory usage for analysis
- Check for application server slow down/freeze/crash
- Check for resource contention/deadlocks
- Database server load and slow down
- Web server crashes, application server logs for exceptions, resource deadlocks
- Collect data for analysis to tune the performance of web server, application server and database server
- If there is an alarm support in the tool through an agent, check for alerts when the activity level exceeds
- If there is a load balancing configuration deployed, check if it is able to distribute the requests.
Result
The result of this test will be a proof of confidence for Continuous Hours of Operation. The data collected in this phase wou
reliability of the system and fix any configuration, component parameters for reliable performance.
Stress testing
Objective
Verify if the software reaches breaking point during low resources, contentions and excessive demands of resources in
Approach
- Increase the load on the system beyond the maximum design load until the system fails for want of resources and/or c
resources (shared memory, queues, socket connections)
- Run iterative load tests that demand resources and look for component breakdowns. The components can be the softw
application server.
- Repeat test if the failure rate is high with additional resources to eliminate resource bottlenecks/contentions
Steps
- Design test cases that
o involve high frequency of virtual users e.g.: searches, large queries
o do large number of simultaneous operations e.g.: registrations
o activate more than one process competing for the same resource.
o require maximum memory
o cause excessive hunting for disk-resident data, high I/O
o large number of slow virtual users connecting which results in large number of socket connections
- Record system response time for each permutation of the stress test case/s
- Record resource utilization and statistics for root cause analysis/bottleneck analysis
- Repeat tests if there is a component break down and check if this condition repeats
- Add additional resources e.g.: Memory, Kernel parameters etc., to see if the break down can be overcom
Result
- The result of this test will list the configuration and will be a measure of the systems robustness to hand
s at the web server end.
Browser Based Test Cases
Scenario
No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
Browser Based Test Cases
Scenario Description
Check that in password input box, text should appear in the form 10*” (Asterisk)
Check the browser ‘Stop’ button while doing any of the functions w.r.t application click on
Check for the expiration of the session.
Check the page downloading time
Check the color coding of the links
Check that the copy right information is in specified area of the site
Check that all information conveyed with color is also available without color.
Check that the site is designed end user in mind - check that application/site fulfills end users expectation
Click on application URL.
Enter a valid user name and leave the password field blank
Leave the username field blank and enter a valid password
Leave the username field blank and also leave the password field blank
Check if the 'user group' of the logged in member is inactivated in between a session
Check whether login follows the standard for the defined type of user groups
Check if the application accepts special characters (out of defined character) in the password of a member login
Check for the 'maximum' number of characters in the password of a member login
Check for the 'minimum' number of characters in the password of a member login
Session validation
Profile refreshing time
Server side caching
Check for the access privilege validation on a 'user group' over each 'application'
Check that the password is not retained on the login page once a user logs in.
Search some feature on site, once it start searching , click on ‘Stop’ button
Right click on a link and select ‘Open in a New Window’
Check the functionalities in all the browsers like different versions of IE, different versions of Netscape etc…
Check when the screen is a Model window user can access the other screens in the application with out closing the model
window
Check the title of the internet explorer window.
Check that the expansion of each abbreviation or acronym is documented where it first occurs.
Check that end users receive documents/information according to their preferences (e.g., language, content type, etc.)
Check that navigation bars is highlighted and access has been given to the navigation mechanism.
Check that the distinguishing information is at the beginning of headings, paragraphs, lists, etc.
Check that pages are usable and if this is not possible, ensure that equivalent information on an alternative accessible page
is available
Check that for time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g.,
captions or auditory descriptions of the visual track) are available.
Check that the end users can't move content, avoid movement in pages unless specified.
Check that any element that has its own interface can be operated in a device-independent manner.
Check the logical tab order through links, form controls, and objects.
Check that equivalents for dynamic content are updated when the dynamic content changes.
Check that search functions are provided, enable different types of searches for different skill levels and preferences.
Check that a skip is allowed for introduction or avoid introductory movies all together
Check that the key navigation links appear first on web page.
Check that the site is designed keeping business goals in mind. Check that site communicates the application or business
objectives.
Check that the site is designed end user in mind - check that application/site fulfills end users expectation
Check that there is no hidden navigation once a end user navigates various controls.
Check that the clear differentiation is given for mandatory and non-mandatory fields
Are labels, text and placement, consistent in color, font, and sizes in all screens?
All input box are standard in height (suggested: not less than 18px and not more than 20px)?
Are the complicated input-boxes supported with Help/hint text? Are they consistent in color, font, and sizes in all screens?
Is background color of the text field “lighter” or in contrast with the font color. suggested : white background for input box
for better readability)
Any pop-up-buttons/icons appearing along with input box and text area should have same size, text, and hyperlink property
(cursor: hand). Do they appear the same across all screens?
Check that the mandatory input fields displays error message when not filled and submitted
Check that "Select All” check box checks all the checkbox available.
Check that the column head and rows are differentiated with font, color, and size
Check that the values in the cell aligned according to the text type
Check that the pagination text consistent in all places. Check that number of items in a table, total items, current page
number, are available.
Check the pagination by entering special characters to the text box area
Check the pagination by entering Junk characters to the text box area
Check the pagination by entering negative numbers [ex:-1] to the text box area
Check the pagination by entering Zero [ex:0] to the text box area
Check that the tab appears in single row and not in two rows? (Not to be confused with sub-menu under each tabs)
Check that the total numbers of tabs visible with the name shortened with ellipses (…) when number of tabs exceeds the
display area?
Is the common content across all tabs visible in all tabs? (Example: “Save” button / “Continue” button and other common
content, if any)
Check that the Buttons type consistent in all screens? ( It could be"text" based or "text and icon" or "just icons" based
wherever applicable)
Check that the Icon-based buttons have hyperlink property (cursor: hand)? (Suggestion : Pop-up, Calendar)
Check that the placement of the same action buttons same in all screens? (Example : If “Save” button is right-aligned, it
should be followed in all places)
Check that the page have a horizontal scroll, including pop-up, error messages, secondary windows etc? (Suggestion : It
should be avoided)
Check the compatibility of browsers, different browser version, different operating systems, and different machines.
Check that site usability from the end user perspective who has disabilities
Once you login into your account and use the back button
Try to open the same link in different windows at the same time
Check for Loging in same user ID and password in different windows