Opened 5 years ago
Closed 4 years ago
#656 closed defect (fixed)
Isolating the test environment
Reported by: | pferreir | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | v1.0 |
Component: | General | Version: | 0.98-dev |
Keywords: | Cc: |
Description (last modified by pferreir)
Right now we have some things "leaking out" of our test environment:
- E-mails - one can solve this either by unifying all the mail sending code and somehow disabling it during testing (or replacing it with something silent or providing test data), or by using some fake SMTP server (fakemail?) - the former would kill 2 ducks in a row;
- Cache and temporary files - this is run over the local Indico setup, and we don't want that. Temporary dirs for temp files and cache should be created and used;
We would like as well to do functional testing using an independent web server, in order to avoid future problems - Python's wsgiref implementation seems at a first glance ideal for this, as it can run Indico.
Like this, we can create "sandboxed" Indico environments for testing, without even touching whatever may be running at the time.
Change History (2)
comment:1 Changed 5 years ago by pferreir
- Description modified (diff)
comment:2 Changed 4 years ago by pferreir
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Already done.