A quick glance about software testing

2.  TESTING
• In general, testing is finding out how well something works. In terms
of human beings, testing tells what level of knowledge or skill has
been acquired.
• In computer hardware and software development, testing is used at
key checkpoints in the overall process to determine whether objectives
are being met.

3. 1. Ensures accountability for a given task
2. Clearly list the responsibilities for various functions to various
people. so that everyone knows his or her work fits into entire project.
3. Complement each other, ensuring no one steps on others
4. Supplement each other so that no task is let unassigned.
RESPONSIBILITIES WHILE TESTING

4. o WHAT IS SOFTWARE TESTING
• Software testing is a process of executing a program or application with the intent
of finding the software bugs.

5.  Software testing is a process that should be done during the
development process. And those process are:
:
• Verification is the process to make sure the product satisfies the
condition imposed at the start of the development phase. In other
words, to make sure the product behaves the way we want it to.
• Validation is the process to make sure the product satisfies the
specified requirements at the end of the development phase. In other
words, to make sure the product is built as per customer
requirements.

6.  WHY SOFTWARE TESTING IS
NEEDED?
1.)Software testing is really required to point out the defects and errors
that were made during the development phases.
2.)It’s essential since it makes sure of the Customer’s reliability and
their satisfaction in the application.
3.)It is very important to ensure the Quality of the product.
4.)It is important to ensure that the application should not result into any
failures
5.) Testing is required for an effective performance of software
application or product.

7. The student will be able to:
1. Understand the impact of software bugs
and importance of software testing
2. Develop skills to find out bugs in any
type of software
3. Use your new testing skills to test not
just the software, but also product
specification the raw code, and even the
user's manual
4. Learn how to test software for
compatibility, usability and cultural issues
5. Discover how to improve your testing
efficiency by automating your test.

8. SOFTWARE QUALITY
ASSURANCE AND QUALITY
CONTROL
(SQA and SQC)

9. SOFTWARE QUALITY
ASSURANCE
 It is error preventive and verification activity.
 the SQA role is to observe that documented standard, process
and procedures are followed as enforced by development
policy.
 Required material is checklist and performed by QA
engineers.

10. SOFTWARE QUALITY
CONTROL
 It is defect detection and validation activity.
 SQC role is to validate the quality of a system and to check
whether this application adheres the defined qualities standard
or not.
 Required material is application and performed by software
tester.

11. SDLC
 The software development lyf cycle
 It is essentially a series of a steps or phases that provide a
model for the development and the management of the
software.

12. steps involve in SDLC
 Requirement analysis
 project planning
 project design
 development
 testing
 implementation
 maintainence

13. SOFTWARE TESTING
LIFE CYCLE
(STLC)

14. STLC
 Every organization has their own predefined STLC steps in
order to make a quality application that help them to adhere
standard quality
 it also have some phased like in SDLC

17. White Box Testing
• Done by Developers.
• It tests the working of applications

18. Black Box Testing
• Done by Testers.
• It tests the functionality of application without
peering into its working.
• Internal behavior of the code is unknown.

19. Grey Box Testing

20. Developer vs Tester
• Developer always wants to see his code working
properly.
• Tester will test the application, make it fail in any
way, and then surely will test how application is not
working correctly.