Professional Documents
Culture Documents
www.testing.com.vn
Author: Khoa Bui
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
1. What is test plan? We should give definition of test plan and sample structure of one test plan
‣Test plan is document to describe the scope, approach, resources, schedule of intended test activities. It identifies others test
items, the feature to be tested, testing tasks, who will do each tasks, test environment, test design technique, risk,
estimation and exit criteria. It’s a record of test planning process
‣ Sample test plan: We don’t answer all things above. Just answer the bold. If Interviewer asking, we will explain based on
their answer
‣ Test plan identifier: Provide the unique identifier for test plan document
‣ Introduction:
‣ Overview of test plan
‣ Purpose of test plan
‣ Any constrains of test plan
‣ Document Scope:
‣ In scope:
Test Items: which software / product to be tested
Features to be tested: which features/function of software/application to be tested
Testing Types: e.g. Smoke Test, Functional Test, UI Test, Cross Browser Test, Usability Test, Regression Test,
End2End Test
Testing Environment: e.g. Windows 7, 10, Mac OSX, Linux
No requirement test: List anything which we test without requirement (e.g. test performance of software)
‣ Out of scope: Security Testing…
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
1. What is test plan? We should give definition of test plan and sample
structure of one test plan
‣ Constrains: List out some constrains for testing process.
‣ Risk List:
Risk: List out risk of project
Mitigation Strategy: List the way to make risk is not happened
Contingency (if risk is happened): If risk is happened, we will have back-up plan for risk.
‣ Test Approach
‣ Test Schedule
‣ Testing Types: In this section we will list out testing types details including Test Objective,
Technique, Acceptance Criteria
‣ Resources
Human Resources: Manager, Leader, Tester, Developer
Roles of human resources and responsibilities
Testing devices: PC Windows 7, Core i7 8GB RAM, Macbook Pro…
Software: Ranorex with license for 5 users (using for Automation Testing)
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
1. What is test plan? We should give definition of test plan and sample structure of one
test plan
‣ Staffing training if necessary
‣ Deliverable: List out document, report, scripts which team will delivers as Test Plan document, Test Case,
Test Case result, Test Summary Report, Bug Report
‣ Measurement: Defect Density, Defect leakage, Defect Removal Efficiency, Invalid bugs rate
‣ Suspension Criteria: When there’s any problem, impediments, critical issues which blocking testing
progress. QC team will choose suspend testing
‣ Resumption Criteria: When issues is fixed (due to Suspension Criteria), testing team verify and fix. Testing
team can resume
‣ Exit Criteria: Every corporation will define exit criteria based on knowledge and size of project. However, we
can see below as sample:
All test cases are executed
There’s no bug P1, P2, P3 on UAT testing
There’s two minor bugs (P4) on UAT testing
All bugs P1, P2, P3 bugs are fixed and verified by testing team
// We should set document to explain how to the P1, P2, p3, P4 bugs. and list in test plan
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
1. What is test plan? We should give definition of test plan and sample structure
of one test plan
‣ Appendix: This is not required but we should put in test plan, it will help test plan more
valuable
‣ Database: DBA will insert manual 8000 records for testing team to test
‣ Functional test: Testing team will use random data in functional testing
‣ References: We list out all documents which used to define test plan as Specification
Requirement, Non-functional Requirement, Product Design document…
‣ Approvals: Must have a area at the end of test plan, where higher level manager will
approve and sign it
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
4. What should we do when start one project? This is question for manager or
leader, we may not enough experience to do this task. Simple question is:
‣ Get requirement from customer / product owner / BA
‣ Analyze requirement to check which testing types will be applied (automation testing is necessary or not)
‣ Create test plan based on requirement and get approved by higher level manager
‣ Create high level estimate based on requirement or user story (maybe need re-estimate after having the details of each function)
‣ Prepare test environment, resources, training staffs (if necessary)
‣ Design test cases, test data based on acceptance criteria of each function
‣ Review test cases
‣ Execute test cases to verify the function of application. We may do system testing, integration system testing
‣ After system testing is done and reviewed by stakeholders or product owner, deploy on UAT environment
‣ External team will do UAT testing on UAT environment. QC team's able to support test UAT if having avaialble time
‣ If there's any issues on UAT, assign back to Dev to fix
‣ If there's no issues on UAT or no critical issues. UAT team demoed successful to customers. We're able to Sign Off and prepare
related data to deploy on Production with real data
‣ Support customer on production site (analyze issues, verify that is new bug or existing bugs, check that's production problem or
not…)
‣ We will have one or two weeks after deployed on production for checking if having any issues. And plan to fix if that's
happened.
‣ If there's no any news or issues, we're complete one release and prepare to next release
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
‣ A good test case is have enough required information: ID, Summary, Pre-
condition, Steps to execute, Expected Result, Priority
‣ Summary should be short and clearly
‣ Steps to execute should be provided steps by steps correctly
‣ Pre-condition: should provide some special information if it's necessary for test
case
‣ Expected Result: it's based on requirement of application
‣ Test cases must cover all features of application
‣ Test cases must include negative test case
‣ Should be grouped by function or feature. It will help to do regression test or
implement automation test script
‣ Test case should be written simple, easy to understand, ensure other member (not
test case writer) is also able to execute test case
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
7. How to do you make sure team member is able to real perform to test?
‣ Test leader must make sure test cases are written which covered acceptance criteria and include
regression testing if there's impact area
‣ We cannot make sure other testers performa test 100%. But we can verify by cross review
‣ As test leader, I'm taking role as QC, so that I also perform testing. When completing testing, each
tester will cross review testing result of other testers.
e.g I will review result of Tester A. Then Tester A review test result of Tester B…
‣ Test leader test main business workflow of new feature (not run all test scenarios), just make sure
main feature is working fine
‣ In some case, test leader can request other testers demo some special of difficult test cases
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
10.Which levels should be apply to black box and white box testing?
‣ White box testing: Unit Testing, Integration Testing *
‣ Black box testing: System Testing, Acceptance Testing
(*)Someone confuse if we test new feature is integrated with another new feature, is that Integration Testing in
Blackbox Testing? Two features are also integrated together but they are integrated into the application
system, so that it belongs to System Testing (Blackbox Testing)
SOFTWARE TESTING INTERVIEW Q&A – PART 2 (WWW.TESTING.COM.VN)
Khoa Bui
https://about.me/khoabui1912