Defining Testing Requirements For Development Teams Fut

ASCARR1 772 views 18 slides Oct 25, 2011
Slide 1
Slide 1 of 18
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18

About This Presentation

Overview of FUT process and introduction to scripting for development Teams


Slide Content

Test Snippets for
FUT Script
Development
10/25/11Andy Scarr

Agenda
Introductions
Why are we here?
Scripting for
functional
specifications
Review and analysis
of a real functional
specification
Q&A
10/25/11Andy Scarr

Why are we here?
To Improve the quality and coverage of the
functional test scripts detailed in the Functional
Specification documents
To understand what value this can add to the
delivery.
10/25/11Andy Scarr

10/25/11Andy Scarr

Why are we doing this?
Provide clear success criteria to the developer
Provides a scenario in which to put the change into
context
Focus’s the Developer on testing the changes
critical to the business
Improves the quality of the delivery into the
subsequent phase of testing
Earlier rather than late identification of defects is
more cost effective.
10/25/11Andy Scarr

What do they need?
A testable requirement!
Be specific
Provide examples to fill out the required solution
Define the acceptable Ranges / Values / Actions
Define the Unacceptable Ranges / Values / Actions
10/25/11Andy Scarr

Be Realistic!!!
It is impossible to test 100% of the changes
Focus on the high risk areas
Focus on the business priorities
Focus on getting an appropriate level of coverage
10/25/11Andy Scarr

Techniques for Testing
Ranges and Values
Boundary Value Analysis
Looking at the edges of the range
Eg. Range 1-100
Values to be tested: 0, 1,100, 101
Equivalence Partitioning
Looking at valid values within the Range
Eg. Range 1-100
Values to be tested: 2, 99
10/25/11Andy Scarr

Acceptable Numeric Ranges
A requirement states that a specific field on a Form be populated by a user
manually with a Numeric Range 1-5.
The developer may deliver this as a freeform text solution or via a
dropdown selection, this will impact the required scope of the testing
Tests should be written to cover that:
- 1, 2, 3, 4 and 5 be allowed
- 0 and 6 not allowed
- -1, -2, -3, -4, -5 not allowed
- 1.5, 2.75 not allowed
- Alpha characters not allowed
- Symbol characters not allowed
- Blanks not allowed
10/25/11Andy Scarr

Acceptable Numeric Values
A requirement states that a specific field on a Form be populated by a user
manually with a specific Numeric codes (5 digits).
The Developer needs to be aware of what constitutes a valid code
Tests should be written to cover that:
- Valid 5 Digit codes should be allowed
- Valid 4 (Correct but incomplete) and 6 Digit (Correct but elongated)
codes not allowed
- Incorrect Codes not Allowed
- Alpha characters not allowed
- Symbol characters not allowed
- Blanks not allowed
10/25/11Andy Scarr

Finally…..
Effort expended here will have a direct
positive influence on the ultimate quality of
the delivery to the business.
10/25/11Andy Scarr

Review and Analysis of a
Real Functional
Specification
• Early Retirement Request Form
• Can be completed by either the
employee or the manager online
• Each will see different fields and
pre-populated data on entering the
form
• Dates Displayed / Pre-populated
• Free Text fields
• Checkboxes
Screenshot removed for
Security Reasons
10/25/11Andy Scarr

Scripts Defined in the
Functional Specification
Screenshot removed for
Security Reasons
10/25/11Andy Scarr

Things to remember
Pre-populated data
Is it being populated correctly?
Can it be / Should it be amended once populated
Free Text fields
Alpha Only
Numeric Only
Alpha Numeric
Symbols
Checkboxes
Check, uncheck, recheck
10/25/11Andy Scarr

Things to remember
Update Sequences
Top to bottom
Bottom to top
Random updates
Date Formats
YYYYMMDD
DDMMYYYY
\ , . /
Dropdowns
Select, Unselect Reselect
10/25/11Andy Scarr

Things to remember
Role Variances
Different security Levels having different access
Different views of the same form
Different rights
Conflicts in the Design
Beware a copied forward template!
Non Functional
Performance – SLA to bring the form up and to Save it.
10/25/11Andy Scarr

Things to remember
Legal Requirements
Is it compliant to the Disability Discrimination Act 1995
Computer weekly
http://www.computerweekly.com/Home/tags/disability-discrimination.htm
RNIB Website
http://www.rnib.org.uk/xpedio/groups/public/documents/code/InternetHome.hcsp
10/25/11Andy Scarr

Q&A
[email protected]
Mobile :07717224588
10/25/11Andy Scarr