Implementation of Software Testing

SQA and Testing of the Software

1. Implementation of
Software Testing
“Software testers succeed where others fail.”
Anonymous

2. Team Members
•K.K.M.Kodituwakku MMW/13/B1/14

3. What is Software Testing?
Testing is the process of evaluating a
system or its component(s) with the
intent to find that whether it satisfies
the specified requirements or not.

4. The testing process

Planning, design and performance of
testing are carried out throughout the
software development process. These
activities are divided in phases, beginning
in the design stage and ending when the
software is installed at the customer’s site.

6. The main issues that testing methodology has
to contend with are:
■ The appropriate required software quality
standard
■ The software testing strategy.
Decisions about these two issues are
fundamental and must be made before
planning begins.

Determining the test methodology
phase

7. ■ The testing strategy: should a big bang or
incremental testing strategy be
adopted? If incremental testing is preferable,
should testing be performed
bottom-up or top-down?
■ Which parts of the testing plan should be
performed according to the
white box testing model?
■ Which parts of the testing plan should be
performed according to the
automated testing model?

Determining the software testing
strategy

8. Planning the tests

The tests to be planned include:
■ Unit tests
■ Integration tests
■ System tests.

9. Test design
•knowledge of the software, and the
business area it operates on,
•knowledge of the functionality being
tested,
•knowledge of testing techniques
•planning skills to schedule in which order
the test cases should be designed, given
the effort, time and cost needed or the
consequences for the most important
and/or risky features.

10. Testing Types
1.Manual Testing
2.Automation Testing

11. Manual Testing

This type includes the testing of the
Software manually i.e. without using any
automated tool or any script. In this type
the tester takes over the role of an end
user and test the Software to identify any
un-expected behavior or bug.

12. Manual Testing…
•Testers use test plan, test cases or test
scenarios to test the Software to ensure
the completeness of testing. Manual
testing also includes exploratory testing
as testers explore the software to identify
errors in it.

13. Test implementation

Source from:: http://www.cessnock-
ict.net/

14. Automation Testing
•Automation testing which is also known
as “Test Automation”, is when the tester
writes scripts and uses another software
to test the software.

15. When to Automate: Test Automation
should be uses by considering the
following for the Software:

•Large and critical projects.
•Projects that require testing the same areas
frequently.
•Requirements not changing frequently.
•Accessing the application for load and
performance with many virtual users.
•Stable Software with respect to manual
testing.
•Availability of time.

16. How to Automate
•Identifying areas within a software for
automation.
•Selection of appropriate tool for Test
automation.
•Writing Test scripts.
•Development of Test suits.
•Execution of scripts
•Create result reports.
•Identify any potential bug or performance
issue.

17. Tools which can be used for
Automation testing
•HP Quick Test Professional
•Selenium
•IBM Rational Functional Tester
•SilkTest
•TestComplete
•Testing Anywhere
•WinRunner
•LaodRunner
•Visual Studio Test Professional
•WATIR

18. Source from:: http://testdroid.com/

19. References
•Art of Software Testing – by Glenford J.
Myers,Tom Badgett,Corey Sandler
•http://istqbexamcertification.com/what-is-a-
software-testing/
•කේතකරණය හා පරීේෂාව -හ ේමන්ත කුලතිලක
• Software Testing Tutorial -Simply Easy
Learning by tutorialspoint.com

20. This presentation is copy write under the CC License
©Group 5 SQA Team