| Change | User | Description | Committed |
|---|---|---|---|
| 19553 | swellard | Move and rename clients | 9 years ago |
| 19338 | tjuricek | Create custom reporting mechanism to allow for clear "multiple suite" reports... with log...ging! This standardizes on log4j 2 as the backend (was just used on the server side). We have an "in memory appender" that we use to capture results during testing, which we associate with each method run. The whole system spits out yaml files for each suite run, which are then read in via a final task and a single html report is spit out with ... everything... in it. « |
9 years ago |
| 19067 | tjuricek | Add handling to deal with IllegalArgumentException as general "400" level errors from user...s. The different client APIs just need to have their respective techniques provide the error status. « |
9 years ago |
| 19053 | tjuricek | Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that ten...ds 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. « |
9 years ago |
| 18850 | tjuricek | Add the ability to fix jobs in the web API, which we can use to verify the jobs associatio...n with changelists. « | 9 years ago |
| 18818 | tjuricek | Python Client SDK for Helix Web Services | 9 years ago |
| 18810 | tjuricek | First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy"... the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. « |
9 years ago |