Everyone is talking about DevOps but what about DevQA? In addition to analytical and logical thinking testers must know notions of programming and also coding, same as for writing simple unit test scripts. They must know about concepts of databases, web services, build systems and continuous integration. A DevQA stimulates the testing area to expand their knowledge leading out of the comfort zone where once almost manual activities were repeated throughout the development of a system. They have an obligation to reinvent their activities and assisting the team in others, being more integrated and participatory. This is the story how we went from Quality Control to Quality Assistance. How we managed required organisational changes and setting up an automation strategy which lead the way from Quality Control to Quality Assurance. Later on we realised this is not enough as traditional testers help to ship safely by doing the testing, but this can have the side-effect of slowing the team down. Our tester:developer ratio was always low we had to find a way to empower and educate developers to test their features according to quality standards. We evolved this over time also to enforce the “whole team” mentality when it comes to quality. As developers learn to build quality into their features from the start, rework is reduced, and the team can achieve both quick and safe delivery. A DevQA becomes the facilitator for this, instead of the individual performing the tests. This transition is what we called “quality assistance”.

2. 2

3. 3
BACKGROUND
Community Manager Tester Developer
 Since 5 years in games industry
 Quality Assistance Engineer at InnoGames
 Current Project: Forge of Empires

4. 4
STATUS QUO

5. 5
Product
Team
Automation Community

6. 6
PRODUCT TEAM
 Fear of too many interruptions for developers

7. 7
PRODUCT TEAM
 Testers work closely with developer
 Dedicated testers for each product
Planning Requirement Design Development Testing

8. 8
AUTOMATION
 No time and tools
 Complex UI and heavy game logic

9. 9
AUTOMATION
 Save time and speed
 Repeatability
 Maintenance of test suite

10. 10
COMMUNITY
 Involving beta community and community managers
 Introducing gamification

11. 11
COMMUNITY
 Reduction of defects found in production
 Increased quality of bug reports

12. 12
What did we achieve?
ACHIEVEMENTS
 QA input in all stages of the development process
 More than 700 cross-platform UI tests with ~40% coverage
 Reduction of defects found in production by 25%
 Increased customer satisfaction

13. 13
PROBLEMS
Was everything perfect?
 Some bugs still found too late
 Delayed mobile submissions & resubmissions
 QA as bottleneck
 Not enough focus on UI automation

14. 14
WHAT WE HAVE / WHAT WE WANT
Development
Testing
Bug
Dev
Bugfix
Testing
Dev
QA

15. 15
THE VISION
The WHOLE TEAM is responsible for the QUALITY of the product.
QA is responsible for ASSISTING the whole team in PROVIDING high quality.
Every team MEMBER who CONTRIBUTES to the product is responsible
for the entire FEATURE development life cycle.

16. 16
Kick Off Development Demo Done
Dev
QA

17. 17
Influencing Providing Testing
Expertise
Educating
Inspiring Facilitating Identifying
Problems

18. 18
 Want change? Start with yourself
TAKEAWAYS
 Be creative in finding new ways for
utilizing existing resources
 Get everyone on board
 Don’t reinvent the wheel

19. 19
THANK YOU!