IMPORTANCE & NEED FOR TESTING

1. IMPORTANCE & NEED FOR TESTING
NAME: SACHIN PATHANIA
ADMISSION NO: HPGD/JLXXXX
SPECIALIZATION: IT PROJECTS MANAGEMENT
PRIN. L. N. WELINGKAR INSTITUTE OF MANAGEMENT DEVELOPMENT & RESEARCH
(We School)
YEAR OF SUBMISSION: MAY-2021

2.  Software testing may be a process of executing a program or application with the intent of
finding the software bugs.Software testing is an investigation conducted to supply stakeholders
with information about the standard of the software package or service under test.
 Testing is the penultimate step before the launch of the product to the market. It includes
examination, analysis, observation, and evaluation of different aspects of a product.
 Professional Software Tester use a combinations of manual testing with automation tools. After
conducting tests, the testers report the results to the development team. The end goal is to
deliver a quality product to the customer, which is why software testing is so important.

3. Why Software Testing is Important?
 1. Assist in saving money: The testing of software features a big selection of advantages. The
cost-effectiveness of the project happens to be one of the top reasons why companies go for
software testing Services
 2. Security: It is considered to be the foremost vulnerable and sensitive part. There are a bunch of
situations during which the knowledge and details of the users are stolen and that they are used
for the advantages.
 3. Quality of the product: Products should be serving the user in a method or the opposite. It is a
requirement that it's getting to bring the worth, as per the promise.

4.  4. Satisfaction of the customer: As you decide for the simplest project within the saturated
project, you'll be capable of earning the reputation of reliable clients.
 5. Enhancing the development process: With the help of Quality Assurance, you'll find a good array
of scenarios and errors, for the reproduction of the error.
 6. To understand whether the product has any undiscovered hidden features: Users
are never getting to accept any product that has any kind of undiscovered hidden features.
 7. Determining the performance of the software:
If you discover software or application that has low or reduced performance, you'll find that it brings
your reputation down within the market

5. Why is Software Testing Necessary?
Software Testing is necessary because we all make mistakes. Some of those mistakes are unimportant,
but some of them are expensive or dangerous. We need to check everything and anything we produce
because things can always go wrong – humans make mistakes all the time.
Reasons that make testing necessary during SDLC are:
 Makes use of the customers reliability and their satisfaction in the software/application.
 Reduces overall level of risks.
 It is needed for correctly understanding the faults and defects in the system.
 Makes software safe and user friendly.

6.  Allows us to detect defects during the early stages of software development.
 Ensures the quality, effectiveness, and efficiency of the software before its release.
 It is necessary to improve business.
 Creates defect reports and test report, which can be used in future by developer and testers if a
similar issue or defect is encountered by them.
 Helps learn more about software application’s reliability, stability, security, and more.

7. Software Testing Life Cycle

8.  Requirement Analysis:
 Identify sorts of tests to be performed.
 Gather details about testing priorities and focus.
 Identify test environment details where testing is meant to be administered.
 Test Planning:
 Preparation of test plan/strategy document for various sorts of testing
 Test tool selection
 Test effort estimation
 Resource planning and determining roles and responsibilities.
 Test Case Development:
 Create test cases, automation scripts (if applicable)
 Review and baseline test cases and scripts
 Create test data (If Test Environment is available)

9.  Test Environment Setup:
 Understand the specified architecture, environment set-up and prepare hardware and
software requirement list for the Test Environment.
 Setup test Environment and test data
 Perform smoke test on the build
 Test Execution:
 Execute tests as per plan
 Document test results, and log defects for failed cases
 Retest the Defect fixes
 Track the defects to closure
 Test Cycle Closure:
 Evaluate cycle completion criteria supported Time, Test coverage, Cost, Software,
Critical Business Objectives and Quality.
 Prepare test metrics supported the above parameters.
 Document the training out of the project.
 Prepare Test closure report.

10. Testing Methodologies
BLACK BOX TESTING WHITE BOX TESTING

11. Black Box Testing
 It is a way of software testing in which the
internal structure or the program or the code is
hidden and nothing is known about it.
 It’s mostly done by software testers.
 No knowledge of implementation is required.
 It is the behavior testing of the software.
White Box Testing
 It is a way of testing the software in which the
tester has knowledge about the internal structure
or the code or the program of the software.
 It is mostly done by software developers.
 Knowledge of implementation is required.
 It is the logic testing of the software.

12. Different Levels of Testing

13. 1.Unit Testing : checks if software components are fulfilling functionalities or not.
2.Integration Testing : checks the data flow from one module to other modules.
3.System Testing : evaluates both functional and non-functional needs for the testing.
 Unit Testing :
• A Unit is a smallest testable portion of system or application which can be compiled, liked, loaded, and
executed. This kind of testing helps to test each module separately.
• The aim is to test each part of the software by separating it. It checks that component are fulfilling
functionalities or not. This kind of testing is performed by developers.
 Integration Testing :
• Integration means combining. For Example, In this testing phase, different software modules are combined
and tested as a group to make sure that integrated system is ready for system testing.
• Integrating testing checks the data flow from one module to other modules. This kind of testing is
performed by testers.
 System testing :
• System testing most often the final test to verify that the system meets the specification. It evaluates both
functional and non-functional need for the testing.

14.  Acceptance Testing:
• Acceptance testing is a test conducted to find if the requirements of a specification or contract are met as
per its delivery. Acceptance testing is basically done by the user or customer. However, other stockholders
can be involved in this process.
Other Types of Testing:
• Regression Testing
• Buddy Testing
• Alpha Testing
• Beta Testing

15. What is
Automation
Testing?
• Manual Testing is performed by a person's sitting
ahead of a computer carefully executing the test
steps. Automation Testing means using an
automation tool to execute your test suit suite.
• The automation software also can enter test data
into the System under Test, compare expected and
actual results and generate detailed test reports.
• Test Automation demands considerable
investments of cash and resources. Successive
development cycles would require execution of
same test suite repeatedly. Using a test automation
tool, it's possible to record this test suite and re-
play it as needed.

16. Benefits of Automation Testing:
 70% faster than the manual testing
 Reliable in results
 Ensure Consistency
 Saves Time and Cost
 Human Intervention is not required while execution
 Increases Efficiency
 Better speed in executing tests
 Re-usable test scripts
 Test Frequently and thoroughly

17. Conclusion
To conclude, the importance of software testing is imperative. Software testing is a
crucial component of software product development because it improves consistency
and performance. The main benefit of testing is the identification and subsequent
removal of the errors. However, testing also helps developers and testers to compare
actual and expected results in order to improve quality. If the software production
happens without testing it, it could be useless or sometimes dangerous for customers.
So, a tester should wear a unique hat that protects the reliability of the software and
makes it safe to use in real-life scenarios.