In this article, we discuss the basic software testing interview questions and answers.
Software Testing Interview Questions and Answers
1. Why you joined as a tester?
The early era of the market has few companies who were ruling the market with their quality product nowadays tremendous competition is in the market and hundreds, thousands of companies are there who are giving quality products to customers to ensure quality company needs software testers for example in last decade of 20th century and an early decade of the 21st century Nokia is the company who rules market single handed but nowadays companies like apple, Samsung, Vivo and many more are capitating with each other to provide a quality product to their customer. To focus on quality products for their customers. To focus on quality and functionality they need a tester so I choose to become a tester after graduation.
2. Who is a good tester?
The person/tester who can understand the development of the software/requirement correctly from small units to big modules.
3. What are the generic phases involved in the software development life cycle (SDLC)?
There are three generic phases:
a) What
- Requirement Gathering
- Analysis
b) How
- Design
- Development
- Testing
c) Correctness
- Maintenance
4. Is testing start before coding or after coding?
After requirement gathering business analyst (BA) makes business requirement specifications (BRS).
Based on the BRS, BA makes software requirement specifications (SRS).
SRS gives an overview of the whole system/software.
Then at the same time, SRS sends it to the developer and tester.
Testing and coding are parallel processes that start at the same time.
5. What issues tester face during the project or what issues tester face in the project in an excel sheet?
Database connectivity problem.
Build installation problem.
The developer not communicating properly.
Requirements are not clear or incomplete sometimes.
6. What is static testing?
Static testing is the verification process and is also known as quality assurance.
When requirements get collected by the business analyst (BA) he made business requirement specifications (BRS).
After BRS, software requirement specification (SRS) is made in an analysis phase which gives detailed functionality of the software.
All next processes depend upon SRS.
So BA has to review the SRS if any mistake happened or not.
After ensuring that all is OK, then BA forward SRS to the team.
When the design architect creates the design, based on that design developer develops the program.
So the designer also has to review the design.
Similarly, when a developer develops code, he has to compile code to find bugs and removed them. This process is called unit testing.
All these review processes are called static testing and static testing is positive testing.
7. What is dynamic testing?
When the coder handover the final code/build to the tester, the tester test the whole functionality of the system.
Functionality and system testing mean the desired input system should generate the desired output.
Black box testing and grey box testing are involved in this test.
Positive as well as negative testing is done by the tester.
Dynamic testing is also called Quality Control.
8. What are Review and the tester involved in the review?
Yes, the Tester is involved in the test case review and defect analysis review. It’s static testing and the review process is the verification process. The review process is done for quality assurance.
9. Tester involved in a gray box or white box testing?
No, Tester did not get a chance to become part of grey or white box testing.
10. What are software projects?
The software-related problem solved by the software engineer by using software engineering is called software projects.
11. What is the critical functionality of the banking application?
- Security
- Account
- Transaction
12. Is it possible to get zero bug density during maintenance?
Yes, It’s difficult but quite possible.
13. What is your release plan for the project?
In the Waterfall model:
- 1release = 3 months
- 1 year = 4 releases
In the V model:
- 1 release = 3 months
- 1 year = 4 releases
In Agile:
- 1 release (sprint) = 1 month
- 1 month= 1 to 2 modules
- 1 year=12 release
14. What will you do in the V model if customers tell changes in requirements during execution or during production?
If this happens in V model then we accept the changes in requirement but we should take extra money to do the changes.
If the customer’s requirement for a mobile number should be 10 digits and at the time of execution, he want that mobile number should contain 91 before it then we will accept the changes with some extra money.
15. Why V model is expensive?
Because Development and Testing run parallel so it’s costly (Need testing resources from start).
16. Do you involved in agile methodology?
Yes, I am involved in agile methodology in organizations.
17. Which tool you are using for agility?
JIRA is the tool that is used for project and bug management tools and this we are using on agile.
18. Who is the chairperson or main person of the scrum meeting?
Scrum Master