What is the responsibility of the test manager?
- Management from project start to project end
- Test Plan
- Obtain customer approval for delivered products
- Approve intermediate deliverables and release patches to customers
- Record job content for performance evaluation or other billing
- Problem management
- Team management
- Submit weekly status report to test coordinator or SQA
- Attend a weekly retrospective meeting
- Weekly release kpi of all test items
- Mobilize resources for the project
If you find that testers in your organization are still performing deliverable product testing even after obvious defects are identified, what is your approach?
- Acceptance standards should be stricter
- Test cases should be re-evaluated
- If possible, more test cases should be added, including equivalent class segmentation use cases and boundary values
- More test cases should be added to check for invalid conditions
- The criteria for stopping testing should be modified
What is the demand traceability matrix?
The requirements tracking matrix is a matrix that links requirements documents with test cases to ensure that all application requirements are tested during the verification process; check test coverage.
How to choose test tools for the project?
- According to the needs of the project, identify the required features in the automation tool
- Evaluate commercial and non-commercial tools that meet the requirements
- Estimate the cost and benefit of the tool. Cost may include license and training
- Make final decision after consulting with team members
What are the main challenges in the project?
- During the test phase, we are usually within a time limit
- Understanding requirements can sometimes be a challenge
- The application needs to be stable enough to be tested
- Set test priority
- Lack of skilled testers
- Regression Testing
- Frequent demand changes
- Lack of tools, resources and training
What is a test plan?
- A test plan is a document that describes activities and test scope. It is a basic requirement for testing any software product.
What is the type of test plan?
- Overall test plan
- Test level specific
- Test plan specific to test type
What kind of interpersonal skills does the test manager need to have?
- Effective and clear communication
- Establish a good relationship with team members
- Good listening skills and emotional intelligence
- Motivate team members
- Resolve conflicts and ethical issues
What is configuration management?
- Configuration management includes processes for coordinating, controlling, and tracking test artifacts. Test artifacts can include automation code, requirements, documentation, issues, design, change requests, design, etc.
What is the PDCA model?
A test process improvement method. Plan, Do, Check, Act
What is an informal review?
Informal review is a way to check for defects without running code. In the initial stages of the document testing life cycle, informal reviews were implemented several times. Informal comments are not recorded.
What is the type of risk?
- Strategic risks: including budget, communication and management risks
- Project definition risks: including project objectives, scope and demand risks
- HR risk: including skills, team members and organizational risks
- Project schedule risk
What countermeasures should the test manager take to deal with risks?
- Avoidance: Eliminate the risk factors involved
- Reduction: A risk reduction plan that reduces risk impact and takes corrective actions
- Sharing: Transfer risk to another resource, such as insource or insure
- Accept: Accept the risks and prepare a planned budget for those risks
How and what does the test manager evaluate the project?
During the test evaluation, the test manager must evaluate four things: cost, resources, test member skills, and time
- Work breakdown structure: Break the project into smaller parts
- Three-point estimation: Three-point estimation is based on statistical data
- Function Point Method: Give weight to each function and measure the size
What is a three-point estimate?
In the three-point estimation, based on past experience, each task initially produces three values.
- Best case estimate: 120 working hours or 15 days with experienced team members
- The most likely estimate is: 170 hours or 21 days, with sufficient resources and moderate team member experience
- Worst case estimate: 200 working hours or 25 days, and have less work experience with a team
Some test evaluation best practices?
- Increase some buffer time: Having a buffer time is always an advantage, it can help deal with delays caused by unexpected reasons, such as sudden resignation of talent,
- Account resource planning in estimation: Make sure your estimation is realistic and consider key factors such as human resource availability
- Quote past experience: Through your past experience, try to avoid all obstacles or possible obstacles that are most likely to occur
- Stick to your estimate: The estimate is not a complete proof. It may also go wrong. In the early stages of the project, you should re-examine the test evaluation and modify it if necessary
What does the test report include?
- Project information
- Test target
- Test summary
- defect
Best practices for software quality assurance?
- Continuous improvement
- Document file archiving
- Tool use and automation
- Metrics
- Teamwork and sharing SQA responsibilities
What factors can determine the quality of test execution?
- Non-conforming rate: (Number of non-conforming products / Number of qualified products) x100
- Defect leakage rate: (number of missing defects / total number of software defects) x100
How will you deal with team conflicts?
- Due to the diversity of team members' backgrounds and ways of working, the first step is to anticipate and prepare for conflict in the test project.
- The next step is to hold a meeting to assess the project status of the team members. The test manager needs to maintain open communication with everyone so that the team ’s frustration and anger can be vented.
- Finally, team members are required to cooperate and emphasize the importance of their cooperation for project success.
