Read on Twitter
Software Testing Basic Terms every developer should know.
(In Layman Language)
A Thread
(In Layman Language)
A Thread
What is Software Testing ?Process of evaluating a system or its component(s) to find whether it satisfies the specified requirements or not.
Basically finding if the current software is equal to the required software or not
Who does Software Testing?- Software Tester
- Software Developer
- Project Lead/Manager
- End User
When to Start Testing?In short, ASAP
It is done in different forms at every phase of SDLC −
> During the requirement gathering phase, the analysis and verification of requirements.
> Reviewing the design in the design phase
> Testing performed by a dev or a Soft. Tester
When to Stop Testing?Simple answer, it depends on :
- Testing Deadlines
- Completion of test case execution
- Completion of functional and code coverage to a certain point
- Bug rate falls below a certain level and no high-priority bugs are identified
- Management decision
Difference between Verification & ValidationVerification:
- Are yo building it right?
- Done by developers
Validation
- Are you building the right thing?
- Done by software testers.
Software Testing Myths- Testing is Too Expensive
- Testing is Time-Consuming
- Only Fully Developed Products are Tested
- Complete Testing is Possible
- A Tested Software is Bug-Free
- Missed Defects are due to Testers
- Testers are Responsible for Quality of Product
cont
- Test Automation should be used wherever possible to Reduce Time.
- Anyone can Test a Software Application
- A Tester's only Task is to Find Bugs
Software Testing Types:
- Manual
- Automated
Software Testing Methods:
- Black Box
- White Box
- Grey Box
- Anyone can Test a Software Application
- A Tester's only Task is to Find Bugs
Software Testing Types:- Manual
- Automated
Software Testing Methods:- Black Box
- White Box
- Grey Box
Black Box Testing- Testing without having any knowledge of the interior workings of the application is called black-box testing.
- The tester is don't know about the system architecture and does not have access to the source code.
White Box Testing- White-box testing is the detailed investigation of internal logic and structure of the code.
- Tester needs to know the internal workings of the code.
Grey box Testing- Testing with a limited knowledge of the internal workings of an application.
This was Part 1, I thought the thread was getting a little too long.
Do you want a Part 2 ?
Do you want a Part 2 ?
