KEMBAR78
Software Testing Strategies | PDF | Software Testing | Software Engineering
Scribd
Upload
113 views15 pages

Software Testing Strategies

The document discusses different types of testing: formal testing using pre-defined test cases, ad-hoc testing with more freedom and less documentation, and exploratory testing which takes a more systematic approach than ad-hoc testing. It provides scenarios to illustrate when each approach would be best to use. Formal testing is best for critical applications or when requirements are clear. Ad-hoc testing works well for experienced testers or when quick defect finding is priority. Exploratory testing combines ad-hoc testing freedom with supervision and charters to guide the process.

Uploaded by

venkat manoj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
113 views15 pages

Software Testing Strategies

The document discusses different types of testing: formal testing using pre-defined test cases, ad-hoc testing with more freedom and less documentation, and exploratory testing which takes a more systematic approach than ad-hoc testing. It provides scenarios to illustrate when each approach would be best to use. Formal testing is best for critical applications or when requirements are clear. Ad-hoc testing works well for experienced testers or when quick defect finding is priority. Exploratory testing combines ad-hoc testing freedom with supervision and charters to guide the process.

Uploaded by

venkat manoj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Agenda of the Session:

1. Formal Testing
2. Adhoc Testing
3. Exploratory Testing
1. Formal Testing can be also
called as Scripted Testing or
conventional Testing
What is Formal Testing or
Formal Testing mainly focus on
Testing of an application based
on Pre defined process, Pre
designed Test cases.
What is Adhoc Testing?
Adhoc Testing simultaneous
Test design and Execution.
Testers dive into the
application without having pre
defined Test cases and mainly
execute application depends on
1. Creativity
2. Knowledge
3. Passion to conduct Testing
4. Experience or Memory of
past events
During Adhoc Testing more
freedom will be given to the
tester.
Scenario 1: We are working for
Major Banking Domain client,
the Application which we are
supposed to test is very critical
to the client Business/Complex
Application for this scenario
Scenario 2: A tester is working
in the same project from last
5yrs; he gained more
knowledge on
Domain/Business flow, Critical
areas of the app, frequently
failed functions….
Which is the best method to
utilize Tester time?
Scenario 3: Already we have
tested application with 3
rounds by following predefined
set of Test Cases, On the last
day of Testing we are planning
to do final round of sanity
Test/Sanity Regression Test so
which approach is suitable?
Scenario 4: We got a new
project, but due to client
pressure, we are not having
requirements in the project.
But client is asking us to
complete the Testing of
application. Then what we can
do?
Ans: Ask your tester to learn
application by doing adhoc
Testing. Then they can easily
test application
Scenario 5: our client asking us
to rewrite the old version of the
application with new version?
But our client is not having
requirements or documents to
old version of the application
What are the advantageous of
conventional/Formal Testing?
1. Process oriented
2. Systematic approach
3. Proof on what we are
planning to test and how we
are planning to test
4. It Saves Test Execution
time.
5. Test Case design activity
helps to verification because
we write test cases early in
the life cycle. While writing
the test cases we can find
mistakes in requirements
document.

What are the advantageous of


Adhoc Testing?
1. Testers will be given with
the complete freedom, so
tester apply their creativity
and experience
2. Quick finding defects is
possible in adhoc Testing
3. Some time Test cases may
not cover all functionalities
then adhoc Testing helps to
find defects which are not
covered by test cases.
4. No need to spend time on
documentation
5. Test to break attitude
What are the Drawbacks of
Adhoc Testing?
1. No systematic approach
2. No guarantee on what we
have tested and how we
have tested
3. No reusability
4. No Verification in adhoc
Testing
Exploratory Test(ET):
Exploratory Test is a type of
Adhoc Test with more
systematic Approach.
Exploratory Testing Approach in
our project?
1. For each exploratory Test
supervisor will assign
charters
Charter= A functionality
which needs exploratory
Test.
Ex: Inbox
2. Supervisor is responsible
for allocating the Sessions for
each charter
Session= Time frame
required to charter Testing
Session=60mts/100mts…..
3. After session Supervisor
conducts Debrief meeting to
understand observations of
the tester.
3.1 If tester finds more
defects then Supervisor
assigns more sessions to
same charter
3.2 If tester finds charter is
stable then supervisor
assigns one more charter

Note: This Test Can be also


called as
“Session based charter
exploratory Test“
Approach”
Thinking Beyond the
requirements or Out of box
Testing

You might also like