Start a new topic

Expected results for transformer tests

As Alumio integration developer I want the transformer tester to be extended to a complete unit test, so that I can practice a workflow closer to Test-driven development ( ). This way I rely less on QA testing, and regression tests can be done a lot faster, thus speeding up the release cycle. Regression tests are also sometimes needed after an upgrade of Alumio.

Acceptance criteria:

- An expected result can be defined and saved for each transformer test

- The transformer test is runnable, so that expected result and actual result are automatically compared, and the outcome is shown.

- All transformer tests of one transformer are runnable as a set, and the outcomes are shown.

Out of scope / follow-up:

- All transformer tests of all transformers are runnable as a set.

1 person likes this idea
Login or Signup to post a comment