Show Posts
1
Announce Your Software/Service/Product / ZenTao fill up the role of QA tool in Jira
« on: June 12, 2018, 04:07 AM »
I work for Nature Easy Soft, and one of our products is ZenTao. It is open source and for Scrum, so I am trying to let more people know about it. Below is what I wrote for promoting ZenTao. Thanks:)
Jira, in project management, is claimed to be the number one tool used by agile teams. Teams using Jira could easily extend planning, tracking, and reporting with other products of Atlassian, such as collaboration tool HipChat, project planning tool Confluence, and continuous integration tool Bamboo.
However, Jira falls short in test case management. If you have tried Jira, you would know what I am trying to say here. Jira is not an ALM exactly. It is not primarily for QA management given basically anything to be created and tracked via JIRA is considered an issue. As the definition of QA, history, and execution are not separate in JIRA, the rework just increases when QA Managers are scaling QA efforts. Another downside of Jira is its inability to update execution results at each step of the QA. Consequently, QA Managers have limited visibility of the QA progress.
ZenTao, as an Application Lifecycle Management(ALM), covers the whole process of software development project. Its main modules are Project Management, Product Management, and QA management, and integrates task management, story management and bug tracking. ZenTao
underestands that every development team is unique and each of them follows a different set of workflows. Within ZenTao, teams could use extensions to add features they need particularly.
image: My Dashboard in ZenTao
Using ZenTao to do QA management
The basic bug workflow in ZenTao is,
bugs submitted by testers => bugs resovled by developers => bugs accepted by testers => bugs closed by testers.
If a bug did not pass the acceptance, it could be activated for resolution again,
submit bugs by testers => solve bugs by developers => accept bugs by testers => activate bugs by testers =>solve bugs by developers => accept bugs by testers => close bugs by testers.
If a bug recurs after being closed,
submit bugs by testers => solve bugs by developers => accept bugs by testers => close bugs by testers => activate bugs by testers => solve bugs by developers => accept bugs by testers => close bugs by testers.
image: Report a bug in ZenTao
Once developers have asked for a test task, the test task will be generated for them. Then the developers need to relate test cases to it. If the test task needs to be completed by several developers, test cases should be assigned or claimed voluntarily. Go to QA->Build, and choose a build to be tested and click the button to link to test cases.
This is a short introduction of QA management in ZenTao. If you would like to know more or to try it for free, you can go to ZenTao official website.
Jira, in project management, is claimed to be the number one tool used by agile teams. Teams using Jira could easily extend planning, tracking, and reporting with other products of Atlassian, such as collaboration tool HipChat, project planning tool Confluence, and continuous integration tool Bamboo.
However, Jira falls short in test case management. If you have tried Jira, you would know what I am trying to say here. Jira is not an ALM exactly. It is not primarily for QA management given basically anything to be created and tracked via JIRA is considered an issue. As the definition of QA, history, and execution are not separate in JIRA, the rework just increases when QA Managers are scaling QA efforts. Another downside of Jira is its inability to update execution results at each step of the QA. Consequently, QA Managers have limited visibility of the QA progress.
ZenTao, as an Application Lifecycle Management(ALM), covers the whole process of software development project. Its main modules are Project Management, Product Management, and QA management, and integrates task management, story management and bug tracking. ZenTao
underestands that every development team is unique and each of them follows a different set of workflows. Within ZenTao, teams could use extensions to add features they need particularly.
image: My Dashboard in ZenTao
Using ZenTao to do QA management
The basic bug workflow in ZenTao is,
bugs submitted by testers => bugs resovled by developers => bugs accepted by testers => bugs closed by testers.
If a bug did not pass the acceptance, it could be activated for resolution again,
submit bugs by testers => solve bugs by developers => accept bugs by testers => activate bugs by testers =>solve bugs by developers => accept bugs by testers => close bugs by testers.
If a bug recurs after being closed,
submit bugs by testers => solve bugs by developers => accept bugs by testers => close bugs by testers => activate bugs by testers => solve bugs by developers => accept bugs by testers => close bugs by testers.
image: Report a bug in ZenTao
Once developers have asked for a test task, the test task will be generated for them. Then the developers need to relate test cases to it. If the test task needs to be completed by several developers, test cases should be assigned or claimed voluntarily. Go to QA->Build, and choose a build to be tested and click the button to link to test cases.
This is a short introduction of QA management in ZenTao. If you would like to know more or to try it for free, you can go to ZenTao official website.
