Releases: PMA-2020/xform-test
Releases · PMA-2020/xform-test
0.3.2
0.3.1
Bugfixes
- Fixed bug in which program would crash if the last question/prompt in the form was not relevant.
- Fixed a UX bug in which warnings would print twice.
Improvements
- Improved clarity of error messaging.
Developer updates
- Updated test files. Added new test cases.
0.3.0
0.2.0
New Features
- Added 'n/a character
.'. If putting.in the xform-test column, it is the same as leaving the column empty; stating that there are no assertions. - Added character escaping for usage of
:in literal strings, using backslash\.
Updates
- Added necessary requirement that every answerable question prompt not marked as require must at the very least have include a value assertion.
Bugfixes
- Fixed a bug in which assertions were not being checked if a question/prompt was not relevant.
- In tandem with bugfix 1, fixed bug where relevant assertion was sometimes not working correctly; either when assertion was
relevant: falsebut was true, orrelevant: truebut was false. - Via addition of new feature 2, bugs involving usage of the
:character in literal strings were fixed. An assertion string such as '777: 1234' (now written as '777: 1234')no longer triggers a bug where XformTest thinks that '777' is an assertion field (e.g. value assertion, relevant assertion). - Via addition of update 1, related bugs were fixed.
0.1.0
Initial release!
Read the docs: http://xform-test.pma2020.org
Future planned releases
0.3.0
New Features
- Test multiple files with a single command.
- Run multiple tests on a file in a single run.
Developer updates
- Added tests.
- Updates to makefile.
0.4.0
New Features
- Traditional unit tests: Initial support for traditional one-off unit test cases and test suites.
0.5.0
New Features
- Support for choices assertion
Example markup:
{choices: yes no no_response}
General updates
- Informative exception case: When mock
valuecan't be inserted due tochoice_filter - Informative exception case: Failure of
choice_filterassertion