| Summary: | [server] Add test for GET /gitapi/config/{key}/clone/file/{path} | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Tomasz Zarna <tomasz.zarna> | ||||
| Component: | Client | Assignee: | Tomasz Zarna <tomasz.zarna> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | janikpiotrek, Szymon.Brandys | ||||
| Version: | 0.2 | Keywords: | test | ||||
| Target Milestone: | 0.2 | Flags: | tomasz.zarna:
review+
malgorzata.tomczyk: review+ |
||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | gsoc2011 | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 345399 | ||||||
| Attachments: |
|
||||||
|
Description
Tomasz Zarna
Created attachment 197765 [details]
GitConfigHandlerV1.handleGet(...) with source code annot's
Right. Simple fix: https://github.com/pjanik/orion.server/tree/bug349014 I wrote all this code and have the rights to contribute it to Eclipse under the eclipse.org web site terms of use. First of all, I would split the testSetAndUnsetConfigValues method into separate test cases, just like we're trying to do in other tests. For example, I would extract tests for: * getting list of options * getting a single option * adding/setting values with POST * updating values with PUT * removing/unsetting options with DELETE * trying to set a value for non-existing option * and so on... Don't get me wrong, the code is fine, but having a separate test method for each scenario makes the results clearer in case of a failure. Ok, updated (the same branch). Next update, fixed issues mentioned in the comments at github. https://github.com/pjanik/orion.server/commits/bug349014 See my comments here: https://github.com/pjanik/orion.server/commit/3e3844a617ebdedd2b40c6c3b6556fc3e73df92f#bundles/org.eclipse.orion.server.git/src/org/eclipse/orion/server/git/servlets/GitConfigHandlerV1.java-P3 |