Test Management and Utilization of PractiTest at nohana nohana, Inc.　Yoshiyuki Takeda

Yoshiyuki Takeda nohana, Inc. Quality Assurance Unit Manager

No content

Kohei Tai nohana, Inc. Quality Assurance Engineer

Contents ● What is required for QA Team ● Comparison and selection of right test management tools ● After introducing PractiTest

What is required for QA Team

Development Structure QA Engineer Director / Designer Developer (iOS) Developer (Server) Developer (Android) nohana Tester Tester Tester Partner

Lean Startup IDEA PROD UCT DATA MEASURE BUILD LEARN

Mission of QA Team How fast we can go through “Lean Startup”, and how to keep the app quality at the acceptable level while delivering to users as fast as we can.

Comparison and selection of right test management tools

Issues on Test Process Inefficient test case creation and review Dashboard with many numeric formulas and graphs BTS which is hard to customize

Inefficient test case creation and review Create new test cases in spreadsheet from scratch for every project. We created new test cases for every project, so we couldn’t reuse test cases from the past project. Creating and reviewing of test cases was not efficient too. Ver 1.0.0 Ver 1.1.0 Ver 1.1.1 New New New

Dashboard with many numeric formulas and graphs Check the status of test using functions and graphs extensively. Necessary to maintain or modify functions(numerical formula) or graphs every time when new items are added. It is hard to maintain where complicated numerical formulas or graphs.

BTS which is hard to customize We used Trello for outsourcing contractor, and we used Github(issue) for internal use. Couldn’t add fields such as priority or cause of bug. Hard to synchronize Github and Trello. nohana Partner QA Engineer

Points for comparing Test Management Tools ● Pricing ● Functions ○ Requirements management ○ Test case management ○ Test execution and progress management ○ Issue management ○ Import and Export ○ API ○ Markdown ● Support

PractiTest ● Pricing: ENTERPRISE：$49/user/month -> △ ● Functions ○ Requirements management -> ○ ○ Test case management -> ○ ○ Test execution and progress management -> ○ ○ Issue management -> ○ ○ Import and Export -> ○ ○ API -> ○ ○ Markdown -> ○ ● Support -> ○

After introducing PractiTest

Managing Mater Test Cases We stored test cases as Master Test Cases in PractiTest. Depends on the project, we add, modify or select test cases, and execute them.

Pros ● We use test cases as assets and it is more efficient to create test cases than before ● Review is limited to new test cases only, so review time ad cost has been reduced ● It takes time to modify when certain words are widely used (Replacement is easier in spreadsheet) ● It is hard to review each test cases Cons

Utilization of customized Dashboard Check the status of test by customized Dashboard.

● Limitation of customization such as setting progress graph’s period of time to every hour ● Easy for everyone to check the status of test ● Easy to customize and lots of graphs to choose from Pros Cons

Using as BTS and using API Enable to add fields such as priority or cause of bug or whatever necessary. Semi automated Github(issue) and PractiTest using API.

● Necessary to add custom fields for each project(except cloning at the first place) ● Hard to know whom comments intended for due to the lack of mentioning function(added few weeks ago) ● Depends on the priority, developers fix issues ● Semi automation reduces the cost of syncronization ● (want to ) use data from customized fields for Dashboard and bug analysis Pros Cons

Summary ● Tool is one solution to solve issues ● Compare and try many tools ● PractiTest is an excellent tool

THANK YOU