Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 373
- Log:
Initial import of Radiant 0.9.1, which is now packaged as a gem. This is an
import of the tagged 0.9.1 source checked out from GitHub, which isn't quite
the same as the gem distribution - but it doesn't seem to be available in an
archived form and the installed gem already has modifications, so this is
the closest I can get.
- Author:
- rool
- Date:
- Mon Mar 21 13:40:05 +0000 2011
- Size:
- 1005 Bytes
| 1 | take any instance variables already in context and make them available to dataset blocks - this is for nested describes |
| 2 | I'm not sure about this one. It can be very frustrating to lose context of when the state of an iv is modified. |
| 3 | |
| 4 | add ability to clear the database (some tests wanted to guarantee a clear db) |
| 5 | This is acheived with "dataset {}" |
| 6 | |
| 7 | clear database completely at beginning of session, only tables where data was created within a session?? |
| 8 | |
| 9 | clear all dumps on new run of tests |
| 10 | be sure we are capturing a dataset if it has already be captured before during a run |
| 11 | describe what happens when someone has a fixtures file - they get loaded after our datasets, thereby causing all the data in the table of the fixture file (like things.yml) to be deleted - the fixtures are then loaded |
| 12 | look into truncating database instead individual table deletes |
| 13 | allow configuration of dataset |
| 14 | * permatable / global scope |
| 15 | re-evaluation location of some tests that depend on TestCase in non-test/unit tests |
