Software Testing–Basic Guide for beginners
Software Test Types:
Manual
testing: manual
testing is the process of check the software One by one to find
the defects. The testers execute the test cases and generate the
reports manually, without automation tools.
Automation
testing: is the process of testing the software with an
automation tool, to find the defects. Testers execute the test
scripts and automatically generate the test results with automation
tools. Some of the famous automation test tools for functional
testing are QTP/UFT and selenium.
Test
method:
1.
Static Test
2.
Dynamic Tests
Static
Tests: it is also known as checking in Software Tests. Verification
is a static method for verifying documents and files. is the process
to, whether we build the product correctly, that is, to verify the
requirements that we have to check whether we are developing the
product accordingly or not.
Dynamic
Tests: it is also called as validation in Software Tests. Validation
is a process for testing the real product. Validation is the process
of whether we create the right product, ie validate the product that
we have developed is correct or not.
Activities
that are involved in testing the software application
Testing
Approaches:1. White Box Test
2. Black-Box Testing
3.
Gray Box Testing
White
Box Testing: it is also called glass box, Clear Box, structural
Tests. White box Tests use an internal perspective of the system and
programming skills to design test cases. This check is usually
carried out at unit level.
Black
Box Testing: it is also called Behavioral / specification-based /
Input-Output Tests. Black Box Testing is a software test method in
which testers evaluate the functionality of the tested software
without paying attention to the internal code structure.
Grey
Box Testing: Grey box is the combination of White Box and Black
Box Testing. The tester working on this type of test must have
access to design documents. This helps to create more better test
cases.
1. Unit tests
2. Integration tests
3. System tests
4. Acceptance testing
Unit
Testing: Unit Tests are performed to verify that the individual
modules of the source code are working properly. That is, test each
unit of the application separately by the developer in the developer
environment.
Integration
Testing: Integration Testing is the process of testing
connectivity or data transfer between a pair of unit tested modules.
It is AKA I&T-Tests or String Tests. It is divided in a Top-down
approach, Bottom-Up approach Sandwich approach (combination of
Top-Down and Bottom-Up).
System
Testing (end to end test): it is a black box test. The testing of
the fully integrated application, this will also test as an
end-to-end scenario. To ensure that the software works in all
intended target systems. Check thorough examination of each input in
the application to check desired outputs. Testing the user's
experience with the application.
Acceptance
Testing: to receive customer logoff so that software can be
delivered and payments can be received. Types of acceptance tests are
Alpha, Beta and Gamma Tests.
1. Function tests
2. Non-Functional Testing
Functional
tests:in simple way, what the system actually does is
functional tests. To verify that each function of the software
application behaves as specified in the request document. Test all
functionalities by entering them to verify whether the actual output
matches the expected output or not. It falls within the range of
black box Tests and the testers do not have to worry about the source
code of the application.
Non-functional
Tests: in simple terms, how well the system performs is
non-functional tests. It refers to various aspects of software such
as performance test, stress test, stress test, scalability test,
security test, compatibility test etc., emphasis is on improving the
user experience, how quickly the system responds to a request.
Comments
Post a Comment