Darren Burns

Force color

1

## Type of changes - [ ] Bug fix - [x] New feature - [ ] Documentation / docstrings - [ ] Tests - [ ] Other ## Checklist -...

New markdown parser

1

## Type of changes - [ ] Bug fix - [ ] New feature - [ ] Documentation / docstrings - [ ] Tests - [x] Other ## Checklist -...

Add `echo` param to `Console.capture`

7

## Type of changes - [ ] Bug fix - [x] New feature - [ ] Documentation / docstrings - [ ] Tests - [ ] Other ## Checklist -...

Colour output when running on CI platforms that support it

1

GitHub Actions supports colour terminal output, but Rich disables it when it detects it's not writing to a terminal. We should check environment variables, and if we're on a CI...

Test descriptions Markdown should be rendered in failure section

5

When we output a test with the `test-per-line` output mode, the Markdown renders. However, if that test fails, the Markdown doesn't render inside the `Rule`:

Display which plugins have been discovered/loaded

4

In the `SessionPrelude` (the bit of text that prints out at the top of every test session) we should display the names of the plugins that have been discovered (Ward...

Update type annotations, make Ward pass `mypy`, distribute type annotations via PEP561

4

Type annotations have been used for the purpose of improving IDE code assistance so far. MyPy has not been run, and this means that Ward currently does not pass type...

Add note on how to mock to the docs

5

We need a page in the docs that tell users that to mock they should use `from unittest import mock`. We should note that the `mock.patch` decorators don't currently work,...

Add information on how to measure code coverage to the guide

3

Create a separate page in the `guide` section of the documentation which explains how to configure code coverage (i.e. via `coverage run -m ward`).

[CI] Switch to Codecov GitHub action instead of bash uploader

5

Codecov have their own GitHub action. We should migrate to that.