This document outlines a typical daily workflow for a QA member at an internet company, with the goal of understanding their daily tasks and testing process. It involves analyzing new requirements, designing and adapting test cases, performing testing on staging environments, and testing on the live site. The day is broken down into phases including analysis, preparation, staging testing, and live testing. Testing tasks are interspersed with coffee and food breaks to recharge throughout the day. The overall goal is to thoroughly test new features before they are deployed to the live site.

1. To Become the World’s Largest
Internet Platform Outside the
United States and China
Our Mission:
and
a perfect day for a QA member

2. Why this topic? What are the goals?
• Cause „the Boss“ said we have to
• Understand what is the daily work of the/your QA
• Show a possible QA flow
• Recheck your own QA flow in your team
• Have a different view about the magic „QA-topic“, for some
it´s still mystery
• Understand the different between testing and quality
assurance

3. content
• Background for the perfect day
• QA tasks
• Testing phases
• QA flow
• Detail view into the different phases

4. Background for the perfect QA day:
One day = one release
Main focus is the manual testing
8 hours working day ( some Leads have another meaning of „a day“ )
So we can imagine in our example that we have a daily deployment
flow for a small product ( up to 3 countries )
Our example can be adapted on eg. a weekly sprint

5. Tasks for the QA:
Review reqs Adapting tests
Execution of
tests
Feature testingBug reporting Bug retestingRelease report
now let`s bring them together into a daily task plan
Test case design
Adapting plans
Adapting plans
Updating
documentation
Prepare test
strategy

6. different phases
analysing phase
preparation phase
testing phase staging
testing phase live

7. different phases ( weight view )
analysing phase ( 1,5 hours )
preparation phase ( 2 hours )
testing phase staging (3,5 hours )
testing phase live ( 1 hour )
18,75 %
25,00 %
43,75 %
12,50 %

9. 9:00 -10:30 ( 1,5 hours )
1. Get a coffee from the team CTO
2. Start review reqs for new feature(s)
can be a ticket
can be wireframes
can be a click dummy
etc.
3. Check if the requirements force the QA to create new test cases or to adapt
the existing ones
4. clarification with PM if new requirements are “one-time” tests or should be
implemented into the test plan for frequent testing  regression testing
(also check if existing tests or automation tests are effected by the new feature)
analysing phase:

10. 10:30 -12:30 ( 2 hours )
1. Get a coffee and a fruit salad from the team PM
2. Design new test cases and implement them into the existing test plan
3. Adapting old test cases and inform the TA team to adapt the automation
scripts if needed
4. Prepare test plan / build in the test management tool
including clarification with PM: what needs to be tested;
which browser?
which handset?
which test cases? ( different prios possible )
which OS?
5. give estimation about QA test  if holding the timeline will be possible
preparation phase:

11. 13:30 -15:30 ( 2 hours )
1. Get a coffee and a fruit salad and a pizza from the team CTO and PM
( lunch time )
2. Feature testing
3. If needed escalation to project manager if features are failing
4. Creation of bugs / retesting of bugs
5. Run xtests on the feature branch to check side effects
 if there are automated tests, run them!
testing phase staging part 1 ( Feature testing )

12. 15:30 -17:00 ( 1,5 hours )
1. Get a Club Mate from the MD
2. Execute the test case with the given test management tool;
 if there are automated tests, run them!
3. Bug creation and bug retesting
( cause the PM review them very fast and the dev are fixing them much faster )
4. If needed, escalate to project management that the timeline is not reachable:
eg cause of the amount of bugs
5. Collect execution results from test management tool
6. Prepare test report  what was tested? do we have bugs? advice for a live
switch or not
testing phase staging part 2 ( RC testing )

13. 17:00 -18:00 ( 1 hour )
1. Get a beer ( after 18:00 ) from the Founder
2. Execute xtesting on the live environment for all critical parts
 if there are automated tests, run them!
3. Creation and reporting of bugs
4. Reporting about the results of the testing on the live version
5. Ring the bell!
live testing phase:

14. Thank YouThank You.
Questions?

15. © 2015 Rocket Internet SE. All rights reserved.© 2015 Rocket Internet SE. All rights reserved.