1. 21 Apr, 2019 1 commit
  2. 08 Dec, 2017 1 commit
  3. 27 May, 2017 2 commits
  4. 10 Mar, 2017 3 commits
  5. 27 Feb, 2017 1 commit
    • Charles Ferguson's avatar
      Add pylint checks. Improve support for Python 3. · 92289db4
      Charles Ferguson authored
      Pylint complained about a lot of unused variables, all of which should
      now be fixed. The print statement is now using a function form, so as
      to work with Python 3. Raising exceptions a second time is now performed
      through six, rather than faffing about ourselves.
      92289db4
  6. 16 Feb, 2017 1 commit
    • Charles Ferguson's avatar
      Add support for reporting the setup/teardown Class errors. · 3b81711f
      Charles Ferguson authored
      When an error occurs within the setup or teardown code for a class,
      there is no corresponding test for the message to be associated with.
      As such, it is very useful to be able to report the test failure in the
      output so that we can see where the problem occurred.
      
      At present this is only reporting on the failure of the fixture in the
      output. In a future change we may ensure that this is recorded in the
      final results of the tests as well.
      3b81711f
  7. 13 Feb, 2017 1 commit
    • Charles Ferguson's avatar
      Add support for reporting 'setup' and 'teardown' as fixture errors. · f56686d6
      Charles Ferguson authored
      We introduce some new exceptions - FixtureError based exceptions - which
      indicate that the problem was with the test fixture, not the test itself
      and not the SUT (not necessarily). This allows us to report on problems
      which lie with the environment (and possibly the SUT) as distinct from
      the test actually being performed.
      f56686d6
  8. 11 Feb, 2017 1 commit
    • Charles Ferguson's avatar
      Add plugin support for the determination of function names. · a9bdc59a
      Charles Ferguson authored
      Where the functions which failed are in known, we can report them
      with the failure message. This means that we report 'assertEqual' rather
      than 'AssertionError', which is a lot more descriptive. The functions
      that provide this ability are extensions to the plugin interface. They
      can be provided by other plugins to declare their abilities as well.
      This means that it should be possible for the other plugins to be able
      to extend the mechanism used to report failures, without having to play
      with the innards of the TreeOutput plugin.
      a9bdc59a
  9. 05 Feb, 2017 2 commits
  10. 04 Feb, 2017 1 commit
  11. 03 Feb, 2017 1 commit
    • Charles Ferguson's avatar
      Initial import of TreeOutput plugin for Nose. · 8d58e4b3
      Charles Ferguson authored
      The TreeOutput plugin appears to be functional for the simple operations
      that in the tests I'm running. There is a simple manual test available,
      but this relies on examining the output of a given test run to be sure
      of the results.
      8d58e4b3