| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | plugin tests: Added tests for new version assertions | Tristan Van Berkom | 2017-08-30 | 4 | -0/+22 |
| | | |||||
| * | pep8 fixes in plugin test case plugins | Tristan Van Berkom | 2016-12-10 | 7 | -1/+16 |
| | | |||||
| * | Adding test ensuring failure mode when plugin's setup is not a function | Tristan Van Berkom | 2016-11-13 | 2 | -0/+6 |
| | | | | | In the case a plugin's setup is not a function we expect a PluginError. | ||||
| * | Adding test ensuring failure mode when plugin has no setup() | Tristan Van Berkom | 2016-11-13 | 2 | -0/+6 |
| | | | | | In the case a plugin does not provide setup() we expect a PluginError. | ||||
| * | Adding test ensuring failure mode when plugin reports incorrect type | Tristan Van Berkom | 2016-11-13 | 2 | -0/+9 |
| | | | | | | | In the case a plugin defines a setup() which reports a type that is not a subclass of the appropriate type (Source or Element), we expect a PluginError. | ||||
| * | Adding test ensuring failure mode when plugin reports something not a type | Tristan Van Berkom | 2016-11-13 | 2 | -0/+4 |
| | | | | | | In the case a plugin defines a setup() which reports a value instead of a type, we expect a PluginError. | ||||
| * | Adding more plugin tests | Tristan Van Berkom | 2016-11-13 | 8 | -0/+28 |
