(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 can 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.7.7 download link : itest download
Two: 7.7.7 Release description
7.7.7 The details are as follows:
A total of 31 updates. The http interface test can be used for production. The interface test realizes parameterization and the interface is parameter transmission and derivation of interface dependencies . As of 7.7.7 interface test, it has included interface mock, interface encryption, decryption and signature, interface Parameterization, dynamic parameter transmission between interfaces, interface dependency derivation, when building test scenarios, automatically add dependent interfaces and arrange execution relationships according to dependencies, drag to generate broken squares, and drag to extract parameters. Here is also a preview of the new version released at the end of this month, which will support online mind map writing use cases and generating reverse interface use cases based on forward interface use cases
2: The interface test adds parameterization support
3: The interface depends on the topology
4: When the interface test scenario is built, the automatic increase will The dependent interface is entered, and the order is automatically executed.
5: The interface log increases the connection time.
6: The menu style is modified.
7: After the iteration is added, it automatically jumps to the maintenance iteration. The test package page
8: The modification of the test requirement item is added. Permission control
9: The item name is no longer displayed in the use case list.
10: When the scroll bar is dragged down, the left menu is fixed, and it was followed before.
11: Added BUG management. By default, is it only showing the flow to my BUG? Switch
12: Test requirements. If it is a leaf node and there is no use case or BUG, it can be deleted.
13: When all pop-up windows do not drag its border, the window will no longer be scaled.
14: Optimize the generation of the response tree for assertion
15: Extract data from the response data of the interface by dragging and set it as a variable, so that other interfaces can refer to these variables
16: Left is a fixed width, not adaptive before
17: When Mock matches the request header and cookie URL, it no longer checks the value, but only verifies whether there are related parameters.
18: After the BUG is submitted, you can modify the test requirement item
19: Test overview, the bottom grid height of the interface overview is changed to adaptive
20: If the mock file of the mock interface is artificially deleted, in the itest mock interface list, when it is modified, republish and regenerate the mock file
21: Interface test get request plus url URLEncode
22: Generate assertion page in drag and drop, delete When the last node is the last node, all nodes are automatically deleted and saved.
23: Assertions can be generated by dragging, or by handwriting.
24: Measurement analysis is initialized for optimization, much faster than before.
25: Global parameters are added to the interface use case. View tab
26: Assertion and extraction parameters , In addition to drag and drop, add manual editing input
27: The attachment uploaded by the user is larger, and the attachment size can be set. The previous default was 5 M, which is too small
4 bug fixes:
1: If the BUG level and the reason for the introduction of the BUG are disabled, the disabled BUG level and the reason for the introduction will be deleted by mistake.
2: Analysis of the reason for the introduction of the BUG. Sometimes the BUG analysis of all developers will be displayed by default , It’s not for the current project. It’s correct when adding the condition to re-query
3: When there is only one project, set the home page to interface mock, then log in again, and then click "Test" to test the menu, the left menu becomes the "Test" menu, but The grid on the right is still mock
4: BUG is associated with the use case and cannot be deleted
Three: Screenshot of new features of interface testing
Interface data parameterization
The following is the above figure to digitize the value printed when it is executed
Parameterized and printed value after applying encryption algorithm
Interface dependence derived from interface parameter dependence
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, you can also choose the encryption and decryption signature algorithm
The 6.6.6 version used in the above figure, after 7.0.0, you can also choose the encryption and decryption signature algorithm
The 6.6.6 version used in the above figure, after 7.0.0, you can also choose the encryption and decryption signature algorithm
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 (the age can be calculated by day or week), and it can be analyzed according to different versions as conditions
Test environment maintenance
