Service Features

  • Lightening Fast Bug Search

    You can access the information of bugs by scanning QR codes on the screenshots, including those taken in manual tests, which saves you the trouble of entering keywords for searching.

  • Bug Data Filter

    Project team members can filter bug data according to bug sources, modules, statuses, priorities and people who deal with the bugs before to access the statistics of the bugs that they need, which will greatly improve their working efficiency.

  • Automatic Bug Collection

    All of the bug-related data (use cases, steps, logs, screenshots, videos, etc) in testing reports of Testin Enterprise Edition can be automatically added to the bug library of project groups. In this way, project groups can manage and track bugs more efficiently.

Service Advantages

  • Bug Management

    • It can work effectively with testing project management, use case management and other systems. By automatically collecting and managing bugs, it allows developers and testers to cooperate and work more efficiently.
    • The testing results of functionality test, compatibility test, user experience test, automated test, etc. can be imported to the bug library without the need of re-entry; bugs found in different types of tests are categorized neatly; bugs can be entered into the bug library by simply scanning their QR codes.
    • Bug management is carried out on the easy-to-use bug console where bugs are marked in multiple dimensions. Users can keep track of bug status and bug fix without the need to install any software.
  • Traditional Tests

    • Without bug management system, testers can only record bug statistics on Excel and communicate through emails; as for isolated bug systems, each system can hardly work effectively with the entire testing system. Testers and developers have to shift from one system to another, which greatly cuts down their working efficiency.
    • The single Bug mode is unable to reflect the particularity of different test types. Separation of test and bug entry procedures requires secondary entry. As bugs are marked with simplistic tags, the differences of bugs found in varied types of testing tasks cannot be presented. Bug testing and information entry are two separate procedures, which means that the same information has to be entered twice at least.
    • Trivial procedures of installing, setting and maintaining software as well as complicated statistics processing are neither cost-effective nor user-friendly.

Application Scenarios

  • Enterprises wracked by conventional manual bug managing methods want to introduce an easy-to-use bug management system to keep track of bugs.

  • Enterprises suffering from isolated bug management systems want to introduce a unified system so that testers and developers won't need to spend time frequently switching from one system to another.

  • Enterprises want to quantitatively evaluate the working efficiency and results of testers and developers based on bug occurrence, bugs fix, coding quality, etc.