itest open source Agile test management, testOps practitioner, minimalist task management, test management, defect management, test management environment 41, there are a wealth of statistical analysis together. Test kits can assign test cases executed, or it can be built to test iteration (including tasks, test kits, BUG) to organize testing, also have test environment management, there is still a commonly used test measure; for fat version frequently, often demand change, may also be derived by itest embodiment, the line modification is performed, and then introducing the new (synchronized) to the line; and a test flow may be set according to the test strategies, and real-time adjustment; kanban test, iteration can view reports, test package implementation, testing tasks progress, can also be performed directly on billboards use case package.
Online experience 1 http://www.itest.work/demo
Online Experience 2 http://120.78.0.137/demo
v4.5.2 Download : the ITest download
This release updates a total of 24 , including 11 function increased 13 bug fixes. The main use cases may increase the tagging function, aspects of the construction of a test case package, label secondary filter use cases; in another iteration (test program) can be built directly test case package for the relevant management personnel, while in the construction plans, assign test package (package is a collection of test cases using the cases) to different personnel; Another important new feature in the construction test, the allocation rules used in the embodiment of two kinds of original volume, the secondary filter support by tag . Details V4.5.2 follows:
11 enhancements:
1, test case execution packet interface cases, increased export excel Batch performed offline
2, test execution example interface package with increased synchronization (import) Excel to perform off-line batch itest
3, Use Case No. canceled turn BUG function only in transit test
4, iterative menu instead iteration | no plans to facilitate quick testing experience, or have experienced users understand iteration testlink
5, the iteration | plan form, increasing the expected start time property, so there is a real start time and estimated time of three knot speed time-dependent properties, while notes off the property, increasing the iteration | Plan Summary multiline text box
6, in an iterative | under the plan, distribution and use-case package tab increase the ability to create use case package, after creating, directly into the current iteration | under the plan, facilitate test management personnel, create iteration | plan allocated while the test case package (testing tasks), before going to the next test in a single collection, test case management package can build, modify this test to test assignments in both good plan, there are plans other similar tools, test plans only use cases, no test case package, only to see the overall progress of the plan can not look at an individual pace.
7, test add tags function
8, when building test packages, in the present embodiment selection diversity based on the use, by increasing the secondary filter tags may be more convenient and more accurate dispensing with Example
9, with the details of the embodiment, by increasing the label display cases
10, execution interface embodiment, the label is not displayed drop-down selection
11, when new projects check the same name, add conditions to non-logical deletion of the same name when this new project name and has been deleted, it will not prompt the same name
15 bug fixes:
1, when export use cases, more than 2000 to be wrong
2, the new test package and test cases from other existing module package or some of the requirements, use cases assigned, no write allocate use case history
3, repair performed offline use cases, then synchronized to the itest, do not update rate is BUG
. 4, test kits, partitioned with interface cases, no scrollbars left tree, node long time, some nodes can not selected from
5, in Chrome, billboards provided for the first page, the weight Log in, then fill in tasks on billboards progress, error reporting system, this problem only now now in chrome, firefox no problem.
6, from the billboards, test points at the package, the name executor embodiment ,, page execution, the execution Column names Remarks This wrap
7, when the modified test packets, not the new display, for a secondary filtered tag entry
8, from the billboards, point of testing under the package, perform the name, the implementation use case ,, not display case package name, perform iterations use cases have the same BUG in the execution history
9, the new test kits when only add a use case , the time to perform the task which executed twice (by + does not pass) will come out of the implementation rate of 2/2, 1/1 should be in the package test case
execution is not the problem.
10, on the guide map point to New, and then enter project information, and then point to save and create a task in the task window, if not full-screen, can not see the Save button the OK
11, test packages to create failure, suggesting that the success of
12, from iteration, the point iteration, and then switch to test all-inclusive TAB, to see its own is not the executor of the test case package, then a use case title with cases bag to see use cases, can not see the use case details
13, ( and iteration that performance is not the same as the actual BUG) from billboards, the point that they are not holders of a test case package, then use a bag the title's use cases to see use cases, patients can not see the details with.
Screenshots
FIG functional model and boot
Guide the blue text on the chart is hot, you can click, easy to use guide
Line test can be offline processing, resynchronization to the line,
In addition to performing the synchronization lines can be further introduced into a variety of supports, with statistical BUG embodiment shown, the testing requirements decomposition pair,
BUG number and the number of cases with the display on each module
Test packets can dispense test tasks, by a plurality of test packets added to the test iterations, the implementation of the statistical tests
Package task to execute test cases
Available on billboards, fill in the progress of the task, execute test cases bag, or process transfer to the name BUG
On billboards, can be performed in cases directly
Process-driven testing
Process-driven defect in the 26 states in evolution, more precise work anyway live
Engine testing process can automatically calculate and transfer to the evolution of the state who name, and can be adjusted in real time process
Multi-dimensional tests measure
Trend analysis insight into the potential risks of the development process, decision-making basis for the project management and control
The results of data analysis control team efficiency, provide quantitative data to support continuous improvement
Overview test, test managers daily work re-set a good helper, quantitative test Daily
Tester Briefing: there are cases of circumstances testers to write, perform several BUG use case scenario, submission, submitted by BUG
People distributed by the state, submitted by people BUG distribution by type, BUG submitted hierarchically distributed by people, and can make different versions
To analyze the condition
Developers get along BUG Briefing: BUG developers have a number of statistics, but also by the distribution of people by state bug, bug class according to people by distribution,
Press for person bug type distribution, for person by BUG age distribution (days may also be age in weeks), and different versions may be analyzed as a condition
Maintenance testing environment
