Pythoscope 0.4-setup-and-teardown
Code with setup (still no side effects).
During the dynamic run we'll get actual values, not necessarily with any idea how to build them. We'll need a good quasi-serialization mechanism in place that will basically take a live object and change it to code that creates it. In this milestone we'll focus on creating that mechanism in order to generate test cases with proper setup and teardown. Generated code will include mocks, as depending on what we're testing we may not need to create real objects. We'll probably use one of the existing mocking solutions, since there are so many of them. ;-)
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 3 Michal Kwiatkowski
- Blueprints:
- 5 Implemented
- Bugs:
- 1 Fix Released
5 blueprints and 1 bug targeted
| Blueprint | Priority | Assignee | Delivery | |
|---|---|---|---|---|
| Don't use pickle for object serialization | Don't use pickle for object serialization | 4 High | 11 Implemented | |
| Preserve objects identity | Preserve objects identity | 4 High | 11 Implemented | |
| Add support for testing of overridden built in methods | Add support for testing of overridden built in methods | 3 Medium | Michal Kwiatkowski | 11 Implemented |
| Better test stubs | Better test stubs | 3 Medium | 11 Implemented | |
| Change __init__ test name | Change __init__ test name | 3 Medium | Michal Kwiatkowski | 11 Implemented |
| Bug report | Importance | Assignee | Status | |||
|---|---|---|---|---|---|---|
| 295340 | #295340 | Internal Pythoscope error | 4 Medium | Michal Kwiatkowski | 10 Fix Released | |
