Professional Documents
Culture Documents
- sequence of activities conducted during the testing process to ensure software quality goals
are met.
- verification and validation activities
- consists of a series of activities carried out methodologically to help certify your software
product.
Phases of STLC
- Requirement Analysis
- Test Planning
- Test case development
- Test Environment setup
- Test Execution
- Test Cycle closure
API TESTING
- enables communication and data exchange between two separate software systems.
- validates Application Programming Interfaces
- to check the functionality, reliability, performance, and security of the programming
interfaces.
- use software to send calls to the API, get output, and note down the system's response.
SYSTEM TESTING
- testing that validates the complete and fully integrated software product
- evaluate the end-to-end system specifications.
- series of different tests whose sole purpose is to exercise the full computer-based system.
Two Category of Software Testing
Black Box Testing
White Box Testing
NEGATIVE TESTING
- testing that checks a system for unexpected input data and conditions.
- can be anything from a wrong data type to a strong hacking attack.
- to prevent applications from crashing due to negative inputs.
REGRESSION TESTING
- testing to confirm that a recent program or code change has not adversely affected existing
features.
- full or partial selection of already executed test cases which are re-executed to ensure
existing functionalities work fine.
- to make sure that new code changes should not have side effects on the existing
functionalities.
INTEGRATION TESTING
- testing where software modules are integrated logically and tested as a group
- to expose defects in the interaction between these software modules when they are
integrated
- verify if the software modules created by different developers works in unity.
-
SECURITY TESTING
- testing that uncovers vulnerabilities, threats, risks in a software application and prevents
malicious attacks from intruders
- to identify all possible loopholes and weaknesses of the software system which might result
in a loss of information and revenue
AGILE
- AGILE methodology is a practice that promotes continuous iteration of development and
testing throughout the software development lifecycle of the project
- proposes incremental and iterative approach to software design
- broken into individual models that designers work on
- customer has early and frequent opportunities to look at the product and make decision
and changes to the project
- Error can be fixed in the middle of the project.
AGILE TESTING
- can begin at the start of the project with continuous integration between development and
testing
- test plan is written and updated for every release.
- test plan includes types of testing done in that iteration like:
o test data requirements,
o infrastructure,
o test environments, and
o test results
Agile testing involves testing as early as possible in the software development lifecycle. It
demands high customer involvement and testing code as soon as it becomes available. The
code should be stable enough to take it to system testing. Extensive regression testing can
be done to make sure that the bugs are fixed and tested.