(1) Introduction and update instructions of itest
Itest open source agile test management, testOps practitioner, minimal task management, test management, defect management, test environment management, interface testing, interface Mock 6 in 1, and rich statistical analysis. Test cases can be distributed according to test packages for execution, and test iterations (including tasks, test packages, BUGs, and interfaces) can be built to organize test work. There are also test environment management, as well as commonly used test metrics; for frequent releases, frequent requirements Change, itest can also export use cases, modify and execute offline, and import (synchronize) to the online after adding; and can set the test process according to the test strategy, and adjust it in real time; in the test board, you can view the iteration report , Test package execution status, test task progress, and package use cases can also be executed directly on the Kanban board.
Official website http://www.itest.work
Online experience 1 http://www.itest.work/demo
Online experience 2 http://120.78.0.137/demo
v7.1.0 download link : itest download
Two: 7.1.0 Release description
7.0.0 Details are as follows:
A total of 15 updates, mainly UI adjustments, and interface test bug fixes. The notice also look at next month release a new version, the new version will support the interface between chaos and interface parameters passed to send test, generate the interface referenced by the topology-dependent parameters , such as the implementation of the interface A, deduced he will rely on an interface to perform .
2: Menu style optimization
3: All lists are optimized, no horizontal scroll bar is displayed
4: On chrome, sometimes the menu is obviously stuck, optimized
5: New Mock page optimization , The page does not look good.
6: Interface test scene, interface timing task. On the page, the button background is wrong.
7: In several statistical analysis, the unsightly histogram has been beautified.
8: In the interface test scene, add view execution log, The current writing date is displayed as viewing the log, and the log window will pop up with one click. At the same time, the interface name can be clicked.
Click to display interface details.
9: When downloading the use case import template, write the use case type drop-down list and use case priority list for convenience Fill in when importing
8 bug fixes:
1: After setting the mock as the home page, when logging in again, it prompts that the general permission has been recovered and there is no left menu
2: When adding an interface, if the baseUrl is not set and the root RUL in the environment variable is not selected, and the entered URL is not http:
3: When adding and saving the connection, if the execution fails, the interface is not saved successfully; now it is changed to save the interface regardless of whether the execution is passed or not.
4: View the interface execution log, and then when returning to the connection list, click left Menu does not respond
5: On the function guide map, click "Defect Management", or "Use Case Management" or "Test Requirements Management or "Test Metrics" to determine any one of these 4 hotspots, then
jump to the page that was last entered before Page, you should enter the page corresponding to these three hotspots.
6: Fix the problem that the connection is refused or the URL does not respond to the front-end during the test test. The front-end response will display the httpClient error message returned by the back-end.
Three: Screenshot of new features of interface testing
This is an interface of mock, josn data is encrypted,
The first time I tested this interface, I did not encrypt and decrypt algorithms
Test this interface decryption algorithm for the first time
Response is ciphertext
Maintain a good decryption algorithm
Select this decryption in the previous interface
Test again, the result of the interface is decrypted
mock supports the above 4 types of delay
Four: Features Overview view
(1) Functional model
The blue text on the guide map is a hot spot, which can be clicked to facilitate the guide
(B) interface testing functionality Summary view :
Basic process: (1)BaseUrl setting------>(2)Basic authentication setting----->(3)Interface security setting------>(4)Maintenance interface use case---- ->(5) Drag and drop to generate interface assertion------> (6) Build interface test scenario (can be directly added in iteration)--->(7) Manually execute interface test scenario (can be single or One-click execution of all interfaces in the scene) or regular execution of test scenes. There is also an interface mock
1: Overview of interface testing
2: Global settings
3: The interface is fully set
Maintain the encryption, decryption and signature of the interface, upload related classes or JARs, select the maintained encryption, decryption and signature in the interface use case, for itest to call back when it performs the interface test ,
4 : Interface use case maintenance
Interface parameter maintenance is very convenient and friendly to testers,
The 6.6.6 version used in the above figure, after 7.0.0, the encryption and decryption signature algorithm can be selected
The 6.6.6 version used in the above figure, after 7.0.0, the encryption and decryption signature algorithm can be selected
The 6.6.6 version used in the above figure, after 7.0.0, the encryption and decryption signature algorithm can be selected
5: Drag-and-drop square setting
6: Interface scene
In the scene, it can be executed individually, or all interface use cases can be executed with one click, or the execution order can be manually adjusted
7: Interface execution log
8: Perform interface test scenarios regularly
9: Interface mock
(3) Product screenshots and overview of other functions
Test cases can be processed offline and then synchronized online,
In addition to simultaneous offline execution, it also supports a variety of imports. In the use case BUG statistical diagram, the test requirements are broken down,
Display the number of bugs and use cases on each module
The use case library maintains public use cases. In the project, use cases can be imported from the use case library or EXCEL or xmind. When importing, such as requirement items, use case classification, priority, and use case tags, if they do not exist in the system, they will be automatically Created at import
Test tasks can be allocated according to test packages, and test execution statistics can be calculated by adding multiple test packages to test iterations
Perform test case package tasks
On the Kanban board, you can fill in the task progress, execute the test case package, or process the bug that flows to the name
On the Kanban board, use cases can be executed directly
In the use case execution page, a function of turning BUG is added to facilitate the direct turning of BUG during execution, and the automatic test case is not passed. Previously, the use case ID was clicked on the use case list page of the use case package
. It is not convenient to see the specific content of the use case. This is 6.6. 2 The second urgent and convenient function
Process-driven testing
Process-driven defects evolve in 26 states, more accurate anyway
The test process engine automatically calculates the evolving state and the name of the stream to whom, and the process can be adjusted in real time
Connect the BUG link from the email notification of the BUG, which may directly handle the BUG
In the received BUG email, bring a connection and automatically log in to ITEST at one point. At the same time, the BUG handling interface in the email will pop up
Multi-dimensional test measures
Trend analysis provides insight into potential risks in the R&D process and provides decision-making basis for project management and control
Result data analysis controls team efficiency and provides quantitative data support for continuous improvement
Test overview, test manager is a good helper for daily work review, quantitative test daily report
Tester briefing: There are testers writing use cases, executing use cases, the number of submitted bugs, and the number of submitted bugs.
Status is distributed by person, BUG submitted is distributed by person by type, BUG submitted is distributed by person by level, and can be made in different versions
Analyze the condition
BUG briefings for developers: There are statistics on the number of developers’ BUGs, as well as distribution by person according to bug status, and distribution by person according to bug level.
According to the type of bug, it is distributed by person, by person according to the age of the bug (age can be calculated by day or week), and can be analyzed according to different versions as conditions
Test environment maintenance
