Challenges
frequent change in requirements
need to gain cross functional knowledge
setting priorities for testing
in-sprint automation - application stability, there is no seperate environment for automation,
page dom structure will change frequently - a -> span -> div
object identification - objects identified with the given locator, but during run time they are not identified
handling synchronization - network speed, application performance
on clicking a link it is redirecting different urls through manual and automation
Estimations
Work Breadown structure (WBS),
Functional point analysis
Three point estimations -> (B+4M+W)/6, SD(Buffer) -> (W-B)/6
Agile - 1 story point -> 1-2 hrs, 2 strory ponts -> 2-4 hrs, 3 story points -> 4-8 hrs
Metrics
test covergage %, passed test case %, failed test case %, blocked test case %, defects accepted %, defect rejected %, defects deferred %
Product metrics - Defect density,
Quality metrics - Customer satisfaction,
Process metrics
Project metrics
Black box Testing techniques - BVA, Equilance class partitioning,
Sprint ceremonies - Backlog refinment session, Daily standup, Sprint Review, Sprint Retrospective
Test Plan - Objective, Test Scope, Testing types, Estimation Time lines, Resources, Deliverabales, Acceptance and Show stopper criteria
Master test plan, Testing level specific test plan, Test type specific test plan
Risks
Project schedule is too tight -> Set test priority for each of the test activity (mitigation plan)
Unplanned leaves - Cross functional knowledge (mitigation plan)
Tools -> ADO, Jira, Rally, Test Director, ALM (Quality Centre)
Repos - SVN, Git
Best practices - Continuous improvement, Documentation, Team work and shared responsibility
Quality of test execution - Defect rejection ration, Defect leakage ratio
