Developer Testing-Test your Spring boot application with a Precision test tool

Introduction: This article mainly introduces the current mainstream Springboot framework projects and precision testing tools to combine and application, through the accurate testing of data penetration, collection, test cases and code of two-way traceability, data analysis and other unique features of a series of precision testing, to achieve the quality assurance of the project.
　

This environment is divided into the basic environment preparation, springboot environment construction, precision test environment, precision testing and springboot environment docking, such as a complete set of configuration process, users can confirm their deployment process through the flow to the stage point, To troubleshoot issues that may be encountered in your deployment.

One, Spring boot configuration process

1, using the tool

1, Eclipse Java Photon

2, Spring Boot

3, JDK 1.8

4, MySQL 5.7

5, Navicat for MySQL

6, apache-maven-3.5.4

7, 0125pinpoint-agent-1.6.2

8, j2ee_enterprise_key_64bit0614

9, Project: Moxi (HTTPS://GITHUB.COM/DALEIWANG/MOXI)
　

2. Configure the required installation
　

1. Install Eclipse, JDK, MySQL, Nodejs

Note: The installation and installation packages for Eclipse and JDK are available on their own, and the nebula test will provide the installation package for MySQL and Nodejs, but must be provided on the user's own native
There is no installation of MySQL and Nodejs

Scripts to install MySQL and Nodejs
　

1. Extract the Mysql-5.7.16-winx64 installation package and Nodejs installation package from the nebula to the server root directory (for example, the D packing directory).
　

2. Right-click to run as Administrator the automated installation tools provided by the Nebula Mysql_nodejs_install.exe
　

3, enter the directory of Nodejs, return. As shown in the following:

　

4. Enter the absolute path to MySQL (to bin) and then enter. After the program runs, the root password of MySQL can be changed to root to manually close the program.

　

2. Install the Spring boot plugin
Eclipse installs the Spring boot plugin, help-eclipse Marketplace, searches the Spring tools installation STS,

　

can also be downloaded by: Https://spring.io/tools/sts/all,

Download the installation later, Eclipse--help--install new Sofware, Next, next install.
　

3, install Maven
　

Eclipse itself will bring Maven, but instead of having the flexibility to install itself, unzip Apache-maven-3.5.4.zip (for example: E:\apache-maven-3.5.4), configure system variables to add variable names:

Maven_home Variable value = E:\apache-maven-3.5.4,

Path Add Variable value =%maven_home%\bin,cmd Test with Mvn-v The following is the installation success.

　

1,eclipse Replace with native maven

Windows-preferences-maven-installations-add, Path point
E:\apache-maven-3.5.4, check the new apache-maven-3.5.4,apply when loading is complete.

　

2, define local maven dependency library

To modify E:\apache-maven-3.5.4\conf\settings.xml, add the following line of code definitions, for example:
<localrepository>c:\users\luxper.m2\repository</localrepository>,c:\users\luxper.m2\ Repository is my local MAVEN warehouse address.

Eclipse:windows-preferences-maven-user Settings-global settings,browse= E:\apache-maven-3.5.4\conf\ Settings.xml,apply.
　

3, new construction and Operation Engineering

Select Spring Starter Project

　

The project name, defined as Moxi, works to select the web below the Web, then Finesh, and then initializes the associated jar package that downloads maven management.

The engineering structure is broadly as follows:

　

Engineering-Right-click--run as--spring Boot App

To add a debug:

In order to resolve each change to the code and restart the project,
Project--Right---spring tools--add Boot Devtools, then each time you modify the class file will be automatically compiled.
　

4, integrated MyBatis

We have just downloaded MySQL and now we add the Pom.xml file
Build tag plus one line <defaultGoal>compile</defaultGoal> below

　

Then there are MyBatis and MySQL:

org.mybatis.spring.boot mybatis-spring-boot-starter 1.2.0 MySQL mysql-connector-java runtime 　Add data source configuration in the Application.properties file:,! [] (http://i2.51cto.com/images/blog/201808/09/9040d97a91f0f9ec22f6886d70c92918.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Navicat connect to local MySQL, new database moxi, query execution Project git page columns out of SQL statement automatically build the database content required for the project. You can verify that the database is connected successfully by creating model, service, and controller **5, consolidating thymeleaf** adding thymeleaf dependencies! [] (http://i2.51cto.com/images/blog/201808/09/1c57946a0762d5b078bababd7a4cb4da.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Configure application.properties! [] (http://i2.51cto.com/images/blog/201808/09/0e74a4aae4c11e69423b4a89b110a022.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Introduce the file:, introduce the corresponding style, picture and JS file, introduce the page file:! [] (http://i2.51cto.com/images/blog/201808/09/e753c7dc646f1c055c6c5b45838b49e3.png?x-oss-process=image/ Watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) introduced HTML: note Demo and news are also HTML files! [] (http://i2.51cto.com/images/blog/201808/09/4bf964bf7e435b7eda6256ac3f51eb1e.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **6, run the program **eclipse environment running: Run as--spring Boot app package run: Right-click Project Maven-maven install, project directory target folder generate Jar package, cmd run. The initial run of the project will download the required dependent libraries for a long time. After the eclipse environment is running successfully, the interface is like this:! [] (http://i2.51cto.com/images/blog/201808/09/e98c389644fa2d802238451a2dd03b89.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) * * Two, TEST project * * **1, download tools and Tools Configuration * * **2, download the Nebula Test tool from the official website: http://www.teststars.cc/**! [] (http://i2.51cto.com/images/blog/201808/09/709306d7c418d51c46c00ffa9d678a9f.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Configure after download: **2, Nebula test server configuration **ttlangagE.config Configuration Item Description:! [] (http://i2.51cto.com/images/blog/201808/09/8e4b65f1f306525040b226aa5a8d701a.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 1. Run under the Nebula Test Server directory ThreadingTestServer.exe, in the bottom right of the chart to register information, view its time, nebula testing has a two-month experience, if more than two months, the occurrence of key expires, please contact the Nebula Test staff, and submit the service side of the serial code ! [] (http://i2.51cto.com/images/blog/201808/09/61e19f56bc5fd9d629b94dbe5b5c2471.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) ! [] (http://i2.51cto.com/images/blog/201808/09/e33638e1723b7f4e192f1623813a116b.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 2. Contact Nebula Staff to obtain the Key.key file of the current server and replace it with the server directory of the nebula; 3. After starting the ThreadingTestServer.exe in the server directory, the ThreadingTestServerFront.exe in the sibling directory is automatically opened, and the following window is automatically ejected, indicating that the connection is normal. [] (Http://i2.51cto.com/images/blog/201808/09/25a6b058bda5bbcadd3ff6b8bf5f1fa8.png?x-oss-process=image/watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_ zmfuz3pozw5nagvpdgk=) **3, Nebula Test Client Configuration * * Note: The nebula Test connection to the online client requires access to the port 17262/17263. Before logging in, you need to ensure that there are no restrictions on network connectivity. Before opening the client, you need to modify the Server.cfg file under the Ttclient folder to configure the Localip entry as a native IP address that can communicate with the server properly. The reason for configuring this localip is that the client needs to receive dynamic data from the server and configure the local IP address server to transmit the data to the client. After configuring the IP address, double-click Run Ttclient/tt.exe file to enter the Nebula test client. Select File, login, enter the IP address of the Nebula test server and your username and password to log in. As shown in.! [] (http://i2.51cto.com/images/blog/201808/09/7bd0324652acb81a333ccd0ca3afbf54.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **4, Nebula Test Cloud Reporting Platform service started * * 1, running the Nebula Test Ttweb directory Bin\redis-2.4.5-win32-win64\32bit in the redis-server.exe! [] (http://i2.51cto.com/images/blog/201808/09/602559e453dda91232b50719a9f5fce3.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 2, run the Nebula Test Ttweb directory startttwebserver.bat! [] (HTTP://I2.51CTO.COM/IMAGES/BLOG/201808/09/488e6e3a958f3117e9092616f7c9ed60.png?x-oss-process=image/watermark,size_16,text_qduxq1rp5y2a5a6i,color _ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=)! [] (http://i2.51cto.com/images/blog/201808/09/92edc7f9ffaa60bfdbd1875cc43391d0.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Visit Webpage Report Web page IP address: 3000**2, create project and version and compile **1, log in Client 2, javaforwindows directory server.cfg configuration file, [SERVER] IP fill in actual IP address, modify [property] field, Sync with server.cfg in the client directory! [] (http://i2.51cto.com/images/blog/201808/09/376d1284b02329e5f4d09d9f540b767c.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 3. Modify the Complierpath.xml configuration file in the Javaforwindows directory Note: project name PROJECT_NAME (fishjoytest) and the version name to be copied Baseversion_name (FISH1) have been created manually , Baseversion_name is an already existing version of the PROJECT_NAME project. Version_name (FISH2) is the version to be compiled. That is: If the FISH2 already exists, then compile directly, if FISH2 does not exist, create a new FISH2, then copy the FISH1 data to Fish2, and then compile. Multiple submodules can be added under the same version as PronamE,proname cannot be repeated, a submodule can be configured with multiple project paths Proname: submodule name project_path: Test program source file path Class_path: Test program class file path! [] (http://i2.51cto.com/images/blog/201808/09/a99ad74f90f525a3dead72aa006fac69.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 4, modify the Javaforwindows directory under the Tt_windows folder Server.ini profile IP is set to the IP address of the client. [] (http://i2.51cto.com/images/blog/201808/09/154116a55124079cfbec28cb37b374a1.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 5. Run Autocompiler.jar on the command line to compile Jre\bin\java.exe-jar autocompile.jar-t D:\J2EE_Enterprise_key_64bit0803\ Compiletoolspkg\javaforwindows Note: The parameter after-T is the directory of the Complierpath.xml file! [] (http://i2.51cto.com/images/blog/201808/09/53b2d1c298b56435ebb5713393954e11.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 6, in the client view data, remember must click Reload file! [] (Http://i2.51cto.Com/images/blog/201808/09/7c0264a4e5e94033a53110c8d8e8c8b0.png?x-oss-process=image/watermark,size_16,text_　qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Because the test needs to run our plug-in code after the completion of the compilation will be in the Java directory in the same layer generated Src-instru directory, the Src-instru directory is compiled plug-and-Go source code, the operation: first the source directory is not installed in the Java directory renamed to Pre_java,　The Src-instru directory generated by the compiled plug-in is then named Java. And the operation of the plug-in code requires our jar package, so we need to modify the customer's Pom.xml file to introduce our Jar service and join the two , add the following code: Systempath needs to be filled in by Javaparser-j2ee.jar and Jeromq-0.3.0-snapshot.jar absolute paths com.zoa javaparser-zmq 1.0 system /d:/j2ee/client/mq/javaparser-j2ee.ja R com.zoa jeromq 1.0 system /d:/j2ee/client/mq/jeromq-0.3.0-snapshot.jar 　After the completion of the Pom file modification can be packaged release after the compilation of a jar package (specific packaging method reference 6, run project) **3, pre-Test preparation * * **1, add data transfer profile * * Data transfer profile is guaranteed to run the data can be sent back to the nebula server. The configuration method is to create a new configuration file under the Usr/local/bin folder in the specific customer test environment Config.cfg file contents are as follows: state=1ip= (IP value write Nebula Test server IP, note to capitalize) (if the publishing environment is a Windows environment, Need to configure the above file in the C packing directory) **2,agent startup Project **cmd input command: Java-javaagent:e:\pinpoint-agent-1.6.2\pinpoint-bootstrap-1.6.2.jar-jar e:\moxi-0.0.1-snapshot.jar! [] (http://i2.51cto.com/images/blog/201808/09/b05b2d5a893779937981fddc8e05faa1.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) E:\pinpoint-agent-1.6.2\pinpoint-bootstrap-1.6.2.jar =agent Path E:\moxi-0.0.1-SNAPSHOT.jar = Project Path This interface indicates a successful run:! [] (http://i2.51cto.com/images/blog/201808/09/cf126932c64322bf818d43c95ca3fc92.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **3, set cookie**1, add teststars.jsp after the project URL, visit the teststars.jsp page for cookie settings! [] (HTTP://I2.51CTO.COM/IMAGES/BLOG/201808/09/CB56e442cef43af2f2070d1d8b910923.png?x-oss-process=image/watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_ 100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) 2, click Setcookie to set the Success page as follows:! [] (http://i2.51cto.com/images/blog/201808/09/8117bd74d90d1748d557487e70d1ffca.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Note: In order to differentiate the test, we set the user name consistent with the current login user of the Nebula client, **4, write the test case **! [] (http://i2.51cto.com/images/blog/201808/09/2716fb7bb26cd162131ee902a47691b9.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Click Add:! [] (http://i2.51cto.com/images/blog/201808/09/de898bd950ce8751fbd10900513174c9.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) ! [] (http://i2.51cto.com/images/blog/201808/09/09a655f77a270604bad05f82bc596924.png?x-oss-process=image/ Watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **5, Project Test * * Access Address: http://localhost:8080/admin/login! [] (http://i2.51cto.com/images/blog/201808/09/7c858c06edb890f0d889934ddb3d2992.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) ! [] (http://i2.51cto.com/images/blog/201808/09/901368375ded65e6f19a7500497b75b0.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) After landing in the page, if you test the content management of the article management of the test cases, select the content management of the article management use cases, click Start, on the page click on the content management of the article management, there will be a corresponding test data transfer over (specific display see the first title of test results: oscilloscope display), Data received after the Click Stop, this article force test completed * * Three, Test results * * **1, oscilloscope waveform display * * First check the test cases, and then click on the beginning of the corresponding test can be done, the test oscilloscope can receive dynamic data and the way the waveform display. [] (http://i2.51cto.com/images/blog/201808/09/6eb246024f39629b65c02092a3da1efc.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Note: The Collected dynamicThe state data is stored in the server-side directory under the Versiondata folder, the corresponding version of the dynamic data stored in the corresponding version of the directory (version number can be viewed in the database management table in the version table) **2, defect management * * In order to allow the test staff to better manage the defects , the use of test cases, code, bug-related methods, accurate testing of the cloud platform using the history of bug tracing function, which makes the same test case in the version iteration, all of the bug situation at a glance, to avoid the changes due to personnel or version changes caused by the same bug troubleshooting time, and repeatedly commit unresolved bugs.! [] (http://i2.51cto.com/images/blog/201808/09/98b5a2a3e35dadc76a99c01ad71dee01.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Chart defect submission and management! [] (http://i2.51cto.com/images/blog/201808/09/04355516630f4a1b3f435dd70f2543ba.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Chart bug Information at a glance **3, coverage * * Coverage visualization for function sc0, True, False, both, Branch, C/DC, MC/DC 7 coverage gives a visual display here is a description for each coverage display: (Take sc0 as an example) sc0 is covered by a statement block whose color-sensitive object is the base statement block (including the suppressed block of invisible statements) where the green label is covered by the statement block. Blue is a block of statements that is not covered. The calculation method is: Overwrite to block/should statistic block! [] (http://i2.51cto.com/images/blog/201808/09/caa34d7694cf4521621a0c0916a06702.png?x-oss-process=image/ Watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) with red marked SC0 coverage, the function list to the right of the coverage of the show:! [] (http://i2.51cto.com/images/blog/201808/09/6f16f333a23ac7c5237f485d383bf08e.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **4, bidirectional traceability refers to the traceability between test cases and the source code by running test cases. According to the test, view the relevant measured source for positive traceability, according to the source code to view the relevant test cases for reverse traceability. Selecting a test case in the test case list, which can be traced back to the content description of the test case, shows the function being tested in the module call graph, or in the module invocation diagram, by clicking on the relevant function, or by tracing the relevant test case. This traceability technology facilitates the user to view and design test cases.　The bidirectional traceability function can be run on the premise that the test case has been run, and the oscilloscope has received the waveform to capture the dynamic data. **1, forward tracking * * Positive traceability refers to the automatic association of test cases and large amounts of code execution information to the level of function and code block, and forward traceability allows you to locate test field faults and defect logic directly at the code level and provide the last run of time series data The detailed design implementation of the automatic recording of the generating function by forward tracing, auxiliary software decoupling and architecture analysis. The advantages of positive traceability are: Quickly locating the code execution logic corresponding to the defect, helping to develop a quick fix defect, tracing the hard-to-reproduce defect, accurately and thoroughly documenting the test case running, providing a large amount of native analytical data for the precision software testing, analyzing and tracking the defects after the accident, and assisting the development for the function realization confirmation. [] (http://i2.51cto.com/images/blog/201808/09/b03de21452f1cb69e4447b6513a27f20.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Click Test Case ChaseBack to this, instead of running a function with a use case, select a function that goes to the logical branch where the function runs through the control flowchart. The following is a positive trace to the code and function call graph:! [] (http://i2.51cto.com/images/blog/201808/09/e3080973e58a7ca07dcc6500c5809417.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) ! [] (http://i2.51cto.com/images/blog/201808/09/f036f29693cea683452b4809f4160794.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **2, Reverse traceability * * Reverse traceability refers to the ability to analyze code associations to provide accurate data for the development of analytical systems and for conformance modification and regression testing analysis. Reverse tracing process: Click on a line of code in the function or function you want to see, and automatically list the test cases that can be tested to that function or branch of the program! [] (http://i2.51cto.com/images/blog/201808/09/98326b2e815b38ca8fa3a69759c8d3d1.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) The selection function goes back to the test case that ran the function, and see the control flowchart and code for the function! [] (http://i2.51cto.com/images/blog/201808/09/79ea5714979f9ed0545a088b8b4af346.png?x-oss-process=image/ Watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Click on the code to go back to the test case that ran the code **5, simple flowchart Display * * Pre-condition: version has data, Associated source code view can be displayed in the source codes, and in the simple control flowchart of the branch block has a specific statement display, there is coverage data, you can easily control the flow chart to show the current coverage of the block information simple control flowchart function, in the form of statement blocks clearly show the function of the internal control logic, The interface can visually see the control flow of the test coverage of each node, in the display, simple control flowchart can also be color to each program block coverage identification, in the thumbnail image of the entire module coverage is very intuitive. (The background color is green to indicate that there is a test case overlay to the block: The SC0 overlay is the reference standard)! [] (http://i2.51cto.com/images/blog/201808/09/9b1051286457746965b81ca371a4818a.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) **6, Presentation of reports * * Select the project and version that the client compiles: Displays some basic information about the selected compiled project, including: Project metrics information, project information, version information, test summary information, test process monitoring trend chart, test equipment composition and distribution map, version coverage summary chart, Summary of Complexity chart items:! [] (http://i2.51cto.com/images/blog/201808/09/ae4f7f6183f7d6245ee16b9de61fd9f7.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Contains project information: Project details version information: Version details test summary information: Test case pass Rate: Bug-free test case Bug Cumulative: Number of bugs submitted after the test case was run current version coverage (SC0): (Number of visible segments/visible segments executed) *100% Ratio Increase: The number of high complexity early warning functions compared to the previous day's SC0 growth margin: Number of functions with high complexity * * Test Case List：** ! [] (http://i2.51cto.com/images/blog/201808/09/52d01ba1528c18707b75b13b4fcdb4c1.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Displays detailed information about the test case that was produced, including the name of the test case, creation time, execution time, correlation function, coverage ratio, operational status, tester, etc. * * coverage by day growth graph: **! [] (http://i2.51cto.com/images/blog/201808/09/fcd058fb52aae4d1972feb4cb22c154c.png?x-oss-process=image/ watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) Coverage by day growth chart, let managers better grasp the test process * * Test Vulnerability list: **! [] (http://i2.51cto.com/images/blog/201808/09/6251ed3b6591ea51654510802aa60f80.png?x-oss-process=image/　watermark,size_16,text_qduxq1rp5y2a5a6i,color_ffffff,t_100,g_se,x_10,y_10,shadow_90,type_zmfuz3pozw5nagvpdgk=) In a program, there are often hundreds of functions, these functions are related to the entire program core, some developers are discarded but have been reluctant to delete, for these large number of functions, "precision testing" by static, dynamic indicators of comprehensive analysis, in a large number of program functions, Through the calculation of direct screening of potential high-risk test vulnerabilities, through the report to give a presentation. Calculate with complexity and coverage? Calculation by function call context and coverage?

Developer Testing-Test your Spring boot application with a Precision test tool