|
| 1 | +3.5.1-p1 (2020.09.01) |
| 2 | +================== |
| 3 | +- Changes |
| 4 | + * Add additional groovy dependencies. |
| 5 | + - json, xml, sql, datetime, templates. |
| 6 | + * Change webpack default profile. |
| 7 | + |
1 | 8 | 3.5.1 (2020.08.31)
|
2 | 9 | ==================
|
3 |
| -* Changes |
| 10 | +- Changes |
4 | 11 | * Support Java 11.
|
5 |
| - * nGrinder now supports Java 11. Controller & Agent supports Java 1.8 or above. |
6 |
| - * Bump several libraries version up. |
| 12 | + - nGrinder now supports Java 11. Controller & Agent supports Java 1.8 or above. |
| 13 | + - Bump several libraries version up. |
7 | 14 |
|
8 |
| -* Trivial Fix |
| 15 | +- Trivial Fix |
9 | 16 | * Remove mobile phone column from NUSER table.
|
10 | 17 | * Make several UI improvements.
|
11 | 18 |
|
12 | 19 | 3.5.0 (2020.07.30)
|
13 | 20 | ==================
|
14 |
| -* New Feature |
| 21 | +- New Feature |
15 | 22 | * Introduce server mode agent
|
16 |
| - * In previous version, nGrinder agents made TCP connections from agent to controller and this made hard to locate a nGrinder controller behind a firewall. From version 3.5.0, nGrinder introduces server mode agent so that a controller make a connection from a controller to agents. |
17 |
| - * See https://github.com/naver/ngrinder/wiki/server-mode-agent |
| 23 | + - In previous version, nGrinder agents made TCP connections from agent to controller and this made hard to locate a nGrinder controller behind a firewall. From version 3.5.0, nGrinder introduces server mode agent so that a controller make a connection from a controller to agents. |
| 24 | + - See https://github.com/naver/ngrinder/wiki/server-mode-agent |
18 | 25 | * Update agents automatically
|
19 |
| - * When the test is executed with older version of agent, it triggers agent auto update. |
| 26 | + - When the test is executed with older version of agent, it triggers agent auto update. |
20 | 27 | * Support GitHub script storage
|
21 |
| - * Users can save and run their test script saved in not only embedded SVN server but also external GitHub repository. GitHub enterprise deployed in each own organization is also supported. |
22 |
| - * See https://github.com/naver/ngrinder/wiki/github-script-storage |
| 28 | + - Users can save and run their test script saved in not only embedded SVN server but also external GitHub repository. GitHub enterprise deployed in each own organization is also supported. |
| 29 | + - See https://github.com/naver/ngrinder/wiki/github-script-storage |
23 | 30 | * Support MySQL
|
24 |
| - * Since 3.5.0, we support H2 and MySQL as databases and fade out Cubrid and provide cubrid-to-mysql migration script. |
25 |
| - * See https://github.com/naver/ngrinder/wiki/mysql-migration |
| 31 | + - Since 3.5.0, we support H2 and MySQL as databases and fade out Cubrid and provide cubrid-to-mysql migration script. |
| 32 | + - See https://github.com/naver/ngrinder/wiki/mysql-migration |
26 | 33 | * Improve test restart time
|
27 |
| - * In previous version, nGrinder agent doesn't cache executed test lib & resources, Therefore, it took long time to execute tests in the case of using large amount of libraries and resource. From nGrinder 3.5.0, the test execution is much faster by sending only changed test resources to agents |
| 34 | + - In previous version, nGrinder agent doesn't cache executed test lib & resources, Therefore, it took long time to execute tests in the case of using large amount of libraries and resource. From nGrinder 3.5.0, the test execution is much faster by sending only changed test resources to agents |
28 | 35 | * Fade out nGrinder-recorder
|
29 |
| - * nGrinder-recorder is no longer supported. |
| 36 | + - nGrinder-recorder is no longer supported. |
30 | 37 | * Support multiple user defined statistics
|
31 |
| - * See https://github.com/naver/ngrinder/wiki/multiple-user-defined-statistic-in-ngrinder |
| 38 | + - See https://github.com/naver/ngrinder/wiki/multiple-user-defined-statistic-in-ngrinder |
32 | 39 | * Ignore error count
|
33 |
| - * Some of users want to continue testing even if there were many errors in the test. So nGrinder 3.5.0 supports that as a test option in advanced configuration panel |
| 40 | + - Some of users want to continue testing even if there were many errors in the test. So nGrinder 3.5.0 supports that as a test option in advanced configuration panel |
34 | 41 | * Support custom classpath
|
35 |
| - * If you want to set classpath for test scripts, you can use this. |
36 |
| - * See https://github.com/naver/ngrinder/wiki/custom-classpath |
| 42 | + - If you want to set classpath for test scripts, you can use this. |
| 43 | + - See https://github.com/naver/ngrinder/wiki/custom-classpath |
37 | 44 |
|
38 |
| -* Modernize |
| 45 | +- Modernize |
39 | 46 | * Back-end
|
40 |
| - * Spring boot |
41 |
| - * Change from spring framework 4 to spring boot 2. |
42 |
| - * Remove embedded Jetty. |
43 |
| - * Hazelcast |
44 |
| - * Use Hazelcast to share data among clusters |
45 |
| - * Reduce load of database. |
46 |
| - * Gradle |
47 |
| - * Use Gradle 6.3 as a build system. |
| 47 | + - Spring boot |
| 48 | + - Change from spring framework 4 to spring boot 2. |
| 49 | + - Remove embedded Jetty. |
| 50 | + - Hazelcast |
| 51 | + - Use Hazelcast to share data among clusters |
| 52 | + - Reduce load of database. |
| 53 | + - Gradle |
| 54 | + - Use Gradle 6.3 as a build system. |
48 | 55 | * Front-end
|
49 |
| - * Vue.js |
50 |
| - * Introduce SPA for imporve responsibility & usability. |
51 |
| - * Use webpack as a module bundler. |
52 |
| - * UX/UI |
53 |
| - * Use Billboard.js to draw charts. |
54 |
| - * Bump bootstrap up from 2 to 4. |
55 |
| - |
56 |
| -* Bug fix |
| 56 | + - Vue.js |
| 57 | + - Introduce SPA for imporve responsibility & usability. |
| 58 | + - Use webpack as a module bundler. |
| 59 | + - UX/UI |
| 60 | + - Use Billboard.js to draw charts. |
| 61 | + - Bump bootstrap up from 2 to 4. |
| 62 | + |
| 63 | +- Bug fix |
57 | 64 | * #490 Fix log file name for agent command line
|
58 | 65 | * #558 Fix agent state API to work in private agent
|
59 | 66 | * #571 Prevent zombie agents from remaining in distributed cache
|
|
0 commit comments