Interview Questions and Answers on Manual Software Testing for Experience Testers
Questions & Answers
Q1. What is the difference between Waterfall Model and Agile Model?
Q2. What is Agile Methodologies?
Agile Methodologies having below features:
1. Sprint Planning - Meeting with entire team, discuss about the sprint activities in the presence of Business Analyst & Stakeholders, Prioritize the work, Define tasks to each team members.
2. Daily Standup Calls - Quick info for each resource, Daily Work Status, Backlog discussion
3. Iterative Reviews - Demo of developed Application in the sprint, Detailed discussion with Business Analyst or Client, Changes discussion, Tester also present in the meeting
4. Retrospective Calls - Feedback session for sprint, what new Learn, what can we do better, Communication between team, Success/Failure discussion on sprint.
Q3. What is Sanity Testing?
Sanity Testing is a technique where testing perform after receiving a software build with minor changes in code, or functionality to a certain that the bug has fixed and no further issue are introduced due to these changes. The goal is to determine that the proposed functionalities work roughly as expected.
Q4. What is Smoke Testing?
Smoke Testing is a Software Testing technique to perform post software build to verify that the critical functionalities of the software are working fine. It is executed before any detailed functional or regression test are executed.
Q5. Is Smoke Testing coming after the Regression Test?
As per the requirement of testing & time availability, the QA team may have to execute Sanity, Smoke & Regression tests on their software build. In such cases, Smoke tests are executed first, followed by Sanity Testing & then based on time availability regression testing is planned.
Q6. What is Bug Life Cycle?
Q7. What is Severity & Priority?
Severity - Severity defines the impact of a defect on the software.
Priority - Priority is defined as the order in which a defect should be fixed. Higher the priority, sooner the defect should be resolved.
Q8. Who decide Severity & Priority in Bug?
Severity - Defines by the Tester or Test Lead
Priority - Defines by the Developer Lead or Sr. Developer
Q9. What is Test Plan?
A test plan is a document detailing the objectives, resources, and processes for a specific test for a software or hardware product. The plan typically contains a detailed understanding of the eventual workflow.
Q10. Important Columns in Test Plan?
Introduction, About the Project, Objective of the Project, Test Project Overview, Test Objectives, Out-of-scope Business process, Dependencies & Baseline Assumptions, Resources, Skillset, References, Risk, Test Cases Links and references, Entry & Exit Criteria etc.
Q11. What is Traceability Matrix?
In software development, a traceability matrix is a document, usually in the form of a table, used to assist in determining the completeness of a relationship by correlating any two baselined documents using a many-to-many relationship comparison.
Q12. What is the difference between Project Planning?
Planning - Project planning is an organized and integrated management process, which focuses on activities required for successful completion of the project. It prevents obstacles that arise in the project such as changes in projects or organization’s objectives, non-availability of resources, and so on. Project planning also helps in better utilization of resources and optimal usage of the allotted time for a project. The other objectives of project planning are listed below.
• It defines the roles and responsibilities of the project management team members.
• It ensures that the project management team works according to the business objectives.
• It checks feasibility of the schedule and user requirements.
• It determines project constraints.
Q13. What is Test Closer Document?
Test Closure is a document that gives a summary of all the tests conducted during the software development life cycle, it also gives a detailed analysis of the bugs removed and errors found. In other words, Test Closure is a memo that is prepared prior to formally completing the testing process.
Q14. What is the difference between Adhoc Testing & Monkey Testing?
Monkey Testing Ad-hoc Testing
Monkey Testing is performed randomly with no specifically predefined test cases Ad-hoc testing is performed without planning and documentation (test cases and SRS)
In Monkey Testing testers may not know what is the system is all about and its purpose In Ad-hoc Testing tester must understand the system significantly before performing testing
The objective of Monkey Testing is to check for system crash Objective of Ad-hoc testing is to divide the system randomly into subparts and check its functionality
& many more to come...
Or visit our website https://www.digitalberry.in/software-testing-courses-classes-pune/