Opened 10 years ago
Closed 9 years ago
#522 closed task (fixed)
Remove dependency on external profile definitions for unit tests
| Reported by: | teckart@informatik.uni-leipzig.de | Owned by: | teckart |
|---|---|---|---|
| Priority: | trivial | Milestone: | VLO-3.1 |
| Component: | VLO importer | Version: | |
| Keywords: | Cc: | Twan Goosen |
Description
Using embedded profile definitions instead (src/test/resources)
Change History (3)
comment:1 Changed 10 years ago by
| Cc: | Twan Goosen added |
|---|
comment:2 Changed 10 years ago by
| Milestone: | → VLO-3.1 |
|---|---|
| Priority: | minor → trivial |
comment:3 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Commited to trunk (r5979). To allow building the application without Internet connection, there is still some work to do as some PostProcessors? rely on external resources (CMDIComponentProfileNamePostProcessor, LanguageCodePostProcessor?, CountryNamePostProcessor?).
Note: See
TracTickets for help on using
tickets.
The best solution is probably to either use an XML catalog (if VTD supports that), or add a level of indirection ourselves, e.g. through a profile locator service with a production implementation that just gets the profile from the source and a test implementation/mockup that gets or reads a profile from the test resources.