1. Explain what is software testing.

It is the process of analyzing any given piece of software to determine if it meets shareholders’
needs as well as detecting defects, and ascertaining the item’s overall quality by measuring its
performance, features, quality, utility, and completeness. Bottom line, it’s quality control.

2. What is quality control, and how does it differ from quality assurance?
Quality control is the process of running a program to determine if it has any defects, as well as
making sure that the software meets all of the requirements put forth by the stakeholders. Quality
assurance is a process-oriented approach that focuses on making sure that the methods,
techniques, and processes used to create quality deliverables are applied correctly.

3. What exactly is manual software testing, and how does it differ from automated software
testing?
Manual software testing is a process where human testers manually run test cases, then generate
the resulting test reports. With automation software testing, these functions are executed by
automation tools such as test scripts and code. The tester takes the end user’s role to determine
how well the app works.
4. What are the advantages of manual testing?
Manual testing’s strengths are:
•It’s cheaper
•You get visual feedback that’s accurate and quick
•It’s ideal for testing minor changes
•It’s perfect for ad hoc testing
•Testers don’t have to know anything about automation tools
•It’s great for testing UI’s

5. On the other hand, what are the drawbacks to manual testing?

Manual testing’s weaknesses are:
•Susceptible to human error
•Some tasks may be difficult to accomplish manually, requiring more time to complete
•The cost adds up, so it’s more expensive in the long run
•You cannot record the manual testing process, so it’s hard to replicate it

6. What kind of skills are needed for someone to become a software tester?
Software testers need skills such as:
•Problem-solving skills
•Excellent written and verbal communication skills
•Detail-oriented
•Able to handle the pressure
•Can work solo or as a team member equally well
•Organizational skills
•Related technical skills
7. Explain what is SDLC.
This is an acronym for Software Development Life Cycle and encompasses all of the stages of
software development, including requirement gathering and analysis, designing, coding, testing,
deployment, and maintenance.

8. What is a test case?

Test case is used to check whether an application complies with its requirements. It is a documented
set of circumstances including prerequisites, input values, and expected outcomes.

9. What is a test scenario?

A test scenario is derived from a use case. It's used to test an application's feature from beginning to
end. Multiple test cases can be accommodated by a single test scenario. When there is a time
constraint during testing, scenario testing comes in handy.

10. What is a test plan?

A test plan is a formal document that specifies the scope of testing, the method to be used, the
resources needed, and the estimated time to complete the testing process. It is derived from the
specifications (Software Requirement Specifications).

11. What is test data?

Test data is information that is used to test software with various inputs and determine whether the
resulting output matches the intended result. This data is generated based on the needs of the
12. What is a test script?
An automated test case created in any programming or scripting language is known as a test script.
These are essentially a collection of instructions for evaluating an application's functionality.

13. What types of manual testing are there? Break them down.
Manual testing is broken down into:
•Black Box
•White Box
•Integration
•Unit
•System
•Acceptance

14. What is black box testing, and what are the various techniques?
Software testers employ black-box testing when they do not know the internal architecture or code
structure. The techniques are:
•Equivalence Partitioning
•Boundary value analysis
•Cause-effect graphing
15. What is white box testing and its various techniques?
Unlike black-box testing, white box involves analyzing the system’s internal architecture and/or its
implementation, in addition to its source code quality. It’s techniques are:
•Statement Coverage
•Decision Coverage

16. Explain the difference between alpha testing and beta testing.
Alpha testing is at the developer’s site before release. Potential clients conduct beta testing at their
websites.

17. What’s the difference between verification and validation?

Verification evaluates the software at the development phase, ascertaining whether or not a
product meets the expected requirements. On the other hand, validation evaluates the software
after the development phase, making it sure it meets the requirements of the customer.

18. What’s a testbed?

It’s not furniture. A testbed is an environment used for testing an application, including the
hardware as well as any software needed to run the program to be tested.
19. What is Sanity testing?
Sanity testing is testing done at the release level to test the main functionalities. It’s also
considered an aspect of regression testing.

20. When should developers implement configuration management procedures?

This should be done during test planning.

21. List the four different test levels

The four levels are:
•Unit/component/program/module testing
•Integration testing
•System testing
•Acceptance testing

22. What’s the difference between a bug and a defect?

A bug is a fault in the software that’s detected during testing time, while a defect is a variance
between expected results and actual results, detected by the developer after the product goes
live.

23. What about the difference between an error and a failure?

If a program can’t run or be compiled during development, it’s an error. If an end-user discovers
an issue with the software, it’s a failure.
24. What’s GUI testing?
This tests the interface between the software and the end-user. Short for Graphics User Interface.

25. When should testing end?

There are a few criteria for ending testing:
•The bug rate has fallen below an agreed-upon level
•The testing or release deadlines have arrived
•The testing budget is out of funds
•A certain percentage of test cases have passed
•The alpha or beta testing periods have ended
•Code, functionality, or requirements coverage have been met at a declared point

26. Why is Software Testing Required?

Software testing is required to ensure the quality and reliability of a software product.
•Testing helps to uncover any bugs, errors, or other issues in the software so that they can be
addressed and fixed before the product is released.
•Testing also ensures that the software meets all the requirements specified by the customer and
works as expected.
•Finally, testing helps to ensure that the software is secure and can withstand malicious attacks.
27. What are the different levels of manual testing?
The different levels of manual testing are:
•Unit Testing
•Integration Testing
•System Testing
•User Acceptance Testing
•Performance Testing
•Security Testing
•Compatibility Testing
•Usability Testing
•Installation Testing
•Smoke testing
•Sanity testing
•Regression Testing

28. Explain the procedure for manual testing?

Manual testing is a process of identifying bugs and errors in a software product without the use of
automated tools. The procedure for manual testing is as follows:
•Identify the scope of testing: The first step of manual testing is to identify the scope of testing.
The range could be a specific module, functionality, feature, or end-to-end system.
•Design test cases: The next step is to design test cases based on the identified scope. The test
cases should include test scenarios, data, expected results, and all other details necessary to
perform the tests.
•Execute the test cases: After designing the test cases, the testers execute them to find any
discrepancies between the expected and actual results.
29. What is the test case?
A test case is a set of conditions or variables under which a tester will determine whether a software
system or one of its features is working as it was originally established for it to do. It may take the
form of input, action, or environmental conditions. In addition, a test case includes requirements, test
steps, verification steps, prerequisites, outputs, and actual results.

30. What's the role of documentation in Manual Testing?

Documentation is an integral part of manual testing. It is essential to document all steps taken in the
testing process to ensure thorough test coverage and accurate results. Documentation provides an
audit trail, which can be used to evaluate past test results and identify areas for improvement.
Additionally, it is a reference for other testers who may be unfamiliar with the system or application
under test.

31. What are the different types of Software testing?

Software testing is classified into two main categories.
1.Functional testing
2.Non-Functional testing
32. Explain Functional Testing
Functional testing is a type of black-box testing. It focuses on the software's functional
requirements rather than its internal implementation. A functional requirement refers to the
system's needed behaviour in terms of input and output.
It checks the software against the functional requirements or specification, ignoring non-functional
characteristics like performance, usability, and dependability.
The purpose of functional testing is to ensure that the software up to snuff in terms of functionality
and to solve the difficulties of its target users.
Some of the types of functional Testing are -
•Unit Testing
•Integration Testing
•Regression Testing
•System Testing
•Smoke Testing
•Performance Testing
•Stress Testing
33. Explain Non functional testing
Non-functional testing examines the system's non-functional requirements, which are characteristics
or qualities of the system that the client has specifically requested. Performance, security, scalability,
and usability are among them.
Functional testing is followed by non-functional testing. It examines aspects that are unrelated to the
software's functional requirements. Non-functional testing assures that the programme is safe,
scalable, and fast, and that it will not crash under excessive pressure.

34. Mention a few advantages of Automated testing.

The following are some major advantages of automated testing -
•Automated test execution is quick and saves a significant amount of time.
•Human mistakes are eliminated during testing when test scripts are carefully prepared.
•CI tools like Jenkins, which may also be set to distribute daily test results to key stakeholders, can be
used to schedule test execution for a nightly run.
•Automation testing uses a lot less resources. Test execution requires nearly no time from QAs once
the tests have been automated. QA bandwidth can be used for other exploratory work.
35. What is Regression Testing?
Regression Testing is a full or partial selection of already executed test cases that are re-executed
to ensure existing functionalities work fine.
Steps involved are -
1.Re-testing: All of the tests in the current test suite are run again. It turns out to be both pricey
and time-consuming.
2.Regression tests are divided into three categories: feature tests, integration tests, and end-to-
end testing. Some of the tests are chosen in this step.
3.Prioritization of test cases: The test cases are ranked according to their business impact and
important functionalities.

36. What is Test Harness?

A test harness is a collection of software and test data used to put a programme unit to the test by
running it under various conditions such as stress, load, and data-driven data while monitoring its
behaviour and outputs.

38. What is a Critical Bug?

A critical bug is one that has the potential to affect the bulk of an application's functioning. It
indicates that a significant portion of functionality or a critical system component is utterly broken,
with no way to proceed. The application cannot be delivered to end users until the critical bug has
been fixed.
39. What is Test Closure?
Test Closure is a document that summarises all of the tests performed throughout the software
development life cycle, as well as a full analysis of the defects fixed and errors discovered. The total
number of experiments, the total number of experiments executed, the total number of flaws
detected, the total number of defects settled, the total number of bugs not settled, the total number
of bugs rejected, and so on are all included in this memo.

40. Explain the defect life cycle.

A defect life cycle is a process by which a defect progresses through numerous stages over the
course of its existence. The cycle begins when a fault is discovered and concludes when the defect is
closed after it has been verified that it will not be recreated.

41. What is System testing?

System testing is a type of testing in which the entire software is tested. System testing examines
the application's compliance with its business requirements.

42. What is Acceptance testing?

Acceptance testing is a type of testing done by a possible end-user or customer to see if the software
meets the business requirements and can be used.
43. What is the difference between manual testing and automation testing?
Manual testing is the process of manually testing software for defects. It requires a tester to
manually execute the test steps and compare the actual and expected results. Automation testing
uses special software to control the execution of tests and compare the results with the desired
results. As a result, automation testing is much faster than manual testing and can reduce the time
required to complete a test cycle.

44. When should you opt for manual testing over automation testing?
Manual testing should be used over automation testing when the tests are particular or require
human interpretation. Manual testing is also better suited for exploratory testing, usability testing,
and testing on multiple operating systems or unique hardware.

45. What are the phases involved in the Software Testing Life Cycle?
The phases involved in the Software Testing Life Cycle are:
•Test Planning
•Test Analysis
•Test Design
•Test Implementation
•Test Execution
•Test Results Analysis
•Test Closure