In this video we have conducted software testing mock interview for QA/Testers/SDET
Test Plan is a document that describes the scope, objective and weight on software testing task whereas Test Strategy describes how testing needs to be done.
Test Plan is used at the project level whereas Test Strategy is used at the organization level.
Test Plan has the primary goal of how to test, when to test and who will verify whereas Test Strategy has the primary goal of what technique to follow and which module to check.
Test Plan can be changed whereas Test Strategy can’t change.
Test Plan is carried out by the test manager whereas the Test Strategy is carried out by the project manager.
1. What are your current roles & responsibilities, team size & brief about project you are working on
2. Lets consider your project went live and client got a critical defect
so your mgr calls your for doing RCA and what will you do in future to avoid such things?
Any Best practices or guidelines/ standards to follow.
3. what is ALM workflow?
ALM workflow includes
Release Specification
Requirement Specification
Test Planning
Test Execution
Defect Tracking
4. Do you have any incident in your career where you found a very special bug
5. Do you think test cases should be maintained or it is just a wastage of time? what is your opinion
6. what is difference between unit & integration testing
7. what is purpose of writing test cases
8. difference between HashMap and Hashtable?
HashMap and Hashtable both implements Map interface and looks similar, however, there is the following difference between HashMap and Hashtable.
HashMap allows null key and values whereas Hashtable doesn’t allow null key and values.
Hashtable is synchronized but HashMap is not synchronized. So HashMap is better for single threaded environment, Hashtable is suitable for multi-threaded environment.
LinkedHashMap was introduced in Java 1.4 as a subclass of HashMap, so incase you want iteration order, you can easily switch from HashMap to LinkedHashMap but that is not the case with Hashtable whose iteration order is unpredictable.
HashMap provides Set of keys to iterate and hence it’s fail-fast but Hashtable provides Enumeration of keys that doesn’t support this feature.
Hashtable is considered to be legacy class and if you are looking for modifications of Map while iterating, you should use ConcurrentHashMap.
9. What is difference between Array and ArrayList? When will you use Array over ArrayList?
Arrays can contain primitive or Objects whereas ArrayList can contain only Objects.
Arrays are fixed-size whereas ArrayList size is dynamic.
Arrays don’t provide a lot of features like ArrayList, such as addAll, removeAll, iterator, etc.
Although ArrayList is the obvious choice when we work on the list, there are a few times when an array is good to use.
10. what is the purpose of defect review meeting
• To help prioritize defect fixes for Implementation, Legacy support, and Conversion teams.
• To discuss and assign priority and severity to defects, discuss the expected turnaround time and the planned turnaround time.
• To monitor and review the progress of defect fixes that is due or overdue as of current date.
• To determine the extent of retesting required due to a fix/ enhancement.
• To escalate defects/ issues to PMO when a quick resolution is required, or in case of a deadlock on ownership of defects/ issues.
• To identify whether defect is assigned to right team
• Identify defects that need to be deferred to subsequent releases
1. When should we stop testing?
Ans. Testing (both manual and automated) can be stopped when one or more of the following conditions are met-
1. After test case execution - The testing phase can be stopped when one complete cycle of test cases is executed after the last known bug fix with the agreed-upon value of pass-percentage.
2. Once the testing deadline is met - Testing can be stopped after deadlines get met with no high priority issues left in the system.
3. Based on Mean Time Between Failure (MTBF) - MTBF is the time interval between two inherent failures. Based on stakeholder’s decisions, if the MTBF is quite a large one can stop the testing phase.
4. Based on code coverage value - The testing phase can be stopped when the automated code coverage reaches a specific threshold value with sufficient pass-percentage and no critical bug.