SOFTWARE TESTING

 Software testing is a method to check whether the actual software product fulfils the expected
requirements and to ensure that software product is defect free.
 It involves execution of software components using manual or automated tools to evaluate whether it is
bug fee or not.
 The primary purpose of software testing is to identify errors, gaps or missing requirements in comparison to
actual requirements.
 The testing team executes the software with an intention of finding error in it and a successful test is one
that finds errors.
1. Manual Testing
Manual testing is a technique to test the software that is carried out using the functions and features of an
application. Which means manual testing will be check the defect manually with trying one by one function
is working as expected.
Advantages of Manual Testing:
 Fast and accurate visual feedback: It detects almost every bug in the software application and is used
to test the dynamically changing GUI designs like layout, text, etc.
 Less expensive: It is less expensive as it does not require any high-level skill or a specific type of tool.
 No coding is required: No programming knowledge is required while using the black box
testing method. It is easy to learn for the new testers.
 Efficient for unplanned changes: Manual testing is suitable in case of unplanned changes to the
application, as it can be adopted easily.
2. Automation Testing
Automated Testing is a technique where the Tester writes scripts independently and uses suitable Software
or Automation Tools to test the software. It is an Automation Process of a Manual Process. It allows for
executing repetitive tasks without the use of a Manual Tester.
Advantages of Automation Testing:
 Simplifies Test Case Execution: Automation testing can be left virtually unattended and thus it allows
monitoring of the results at the end of the process. Thus, simplifying the overall test execution and
increasing the efficiency of the application.
 Improves Reliability of Tests: Automation testing ensures that there is equal focus on all the areas of
the testing, thus ensuring the best quality end product.
 Increases amount of test coverage: Using automation testing, more test cases can be created and
executed for the application under test. Thus, resulting in higher test coverage and the detection of
more bugs. This allows for the testing of more complex applications and more features can be
tested.
 Minimizing Human Interaction: In automation testing, everything is automated from test case
creation to execution thus there are no changes for human error due to neglect. This reduces the
necessity for fixing glitches in the post-release phase.

Need & importance of software testing

 Find bugs or errors in the developed software.
 Resolve bugs before delivery of software.
 Save your money for the long term as if bugs are caught in the earlier stage of software testing then it
costs less to fix.
 Security and satisfaction after deployment.

Types of Software testing

1. White box testing
2. Black box testing
3. Grey box testing
1. White box testing :
o It is a software technique in which internal structure, design and coding of software are tested.
o It is done to verify the flow of input-output in the software and to improve design, usability and
security.
o In this testing, programing skills are required to design test cases.
o In white box testing, code is visible to the testers so it is also called clear box testing, Open box
testing, transparent box testing, and glass box testing.
o It focuses on checking of predefined inputs against expected and desired outputs.
o In white box testing various tests are performed , like :
 Path testing
 Loop testing
 Condition testing
 Memory consumption testing
 Performance testing
2. Black box testing :
o It is a software technique in which the functionalities of software are tested without having
knowledge of internal code structure, implementation details and internal paths.
o It is entirely based on software requirements and specifications and mainly focuses on input and
output of software.
o For example, we use an operating system, a website, or our own custom application and we can
perform black box testing by just focusing on the inputs and outputs without knowing the internal
code/implementation.
o It is also known as behavioral testing or specification based testing.
3. Grey box testing :
o It is combination of black box and white box testing.
o In this technique, the tester tests the software with partial knowledge of the internal working
structure.
o This type of testing is mainly used in web based applications as if any error is caught by the tester,
then it is resolved in real-time.
o It helps to test both presentation layer as well as internal coding structure of a software.

Types of Black box software testing

1. Functional testing
2. Non-functional testing

Functional testing :

o It is a type of black box testing in which the testers identify what an application is supposed to do
and runs a series of tests to make sure that the software perform as expected.
o The tester will check all the components systematically against requirement specifications.
It involves testing of user interface, APIs, Database, Security, Client/Server communication etc.
o The testing can be done either manually or using automation.
o Functional testing is executed before non-functional testing.
o Functional testing basically involves (levels of functional testing):
1. Unit testing
2. Integration testing
3. System testing
4. Regression testing
5. User acceptance testing
 1. Unit testing :
o In this testing, the tester tests every individual unit or module of the software.
o It is carried out during the coding phase of software development.
o It is typically done by the developer.
o It is done to ensure each module is working correctly.
2. Integration testing :
o It is the second level of functional testing and is done after the unit testing.
o During the development of the software , two or more modules are integrated with each
other to work together as a group. So, in integration testing we test this group of modules
as a whole.
o It is done to test the data flow between dependent modules or interaction between two
features/modules.
3. System testing :
o It is the third level of functional testing and is done after integration testing.
o In system testing, the tester validates the complete and fully integrated software product.
o The purpose of a system test is to evaluate the end to end system specifications.
4. Regression testing :
o Whenever any change in a software is made, it may be possible that other areas within
the software have been affected by this change.
o In regression testing the tester verifies that a fixed bug has not adversely affected the
existing features of software.
5. User acceptance testing :
o It is the last level of functional testing.
o It verifies whether the software is fulfilling the initial goals according to the requirements.
o It performed by the end user or the client to verify / accept the software before the
development of software for production.
Non-Functional testing :
o In this testing, the tester tests the software for non-functional aspects like security, efficiently,
usability, flexibility, portability and much more.
o It is performed to optimize the software for client / users before production.
o It helps to improve the product behavior and technology used.
o Types of non-functional testing.
1. Performance testing :
o Performance testing refers to look out performance symptoms and issues of the
software like slow response, long load time, easy overloading, poor scalability, high CPU
and disk usage etc.
o We also test the software with work load in order to measure performance as the work
load increases.
2. Usability testing :
o Usability testing is also known as user experience testing and is a method to measure
how easy and user-friendly a software is.
o A few number of target users use the software to expose usability defects.
o It mainly focuses on user’s ease of using the software, flexibility of software and ability
of software to meet its objective.
3. Compatibility testing :
o In compatibility testing, we check the functionality of software on different hardware
platforms, networks, and browsers to find out whether it is working as expected or not.
o The software must be adaptive for all kind of the users irrespective of what device they
use, that is what we test in compatibility testing.