# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 19553 | swellard | Move and rename clients | ||
#5 | 19169 | tjuricek | JavaScript Client SDK jobs CRUD test, with supprt for "additionalProperties" in the swagger definition. | ||
#4 | 19098 | tjuricek |
JavaScript Client SDK labels spec CRUD tests. Identified another parameter naming conflict, which only pops up in the javaScript client because I didn't choose to automatically rename parameters for people. (I don't think it's a good idea to just say "label0", "label1", etc., especially when they're different types.) |
||
#3 | 19095 | tjuricek |
JS Client SDK branch spec CRUD test Added URL component encoding on path parameters. |
||
#2 | 19065 | tjuricek |
Revised Javascript Client SDK documentation to meet the new API, with fixes. Added a couple of basic tests, and added archival of the different testng XML output. The main major fix is to handle array output better. |
||
#1 | 19053 | tjuricek |
Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that tends to be similar in approach to the other clients, based on the swagger definition for the platform version. Importantly, client SDK tests are individual scripts (that run under node) that are actually controlled via TestNG. This approach now lets us use a consistent test reporting format so we can at least collect reports from each of the jobs. The documentation is still in progress, that I want to validate as the tests are generated. |