Visualizing-EUnit-tests icon indicating copy to clipboard operation
Visualizing-EUnit-tests copied to clipboard

This project aims to visualize test cases written in Erlang in a graphical finite state machine representation. The aim is to visually evaluate the quality of a test suite.

Results 8 Visualizing-EUnit-tests issues
Sort by recently updated
recently updated
newest added

Design of interactions so that test sets and FSMs can be refined on the basis of feedback provided from FSM extraction on existing sets.

Need to investigate the literature for algorithms which can work with positive examples only.

Negative tests tend not to get written as readily as positive ones, particularly in testing stateful systems. Examples are useful for testing our basic extraction algorithms.

Need to extend static tracing to handle the issues for dynamic tracing - file handling - coverage of macros - coverage of test representations

Need to cover - simple tests: {ModuleName, FunctionName}, numbered simple tests - {module, ModuleName}, … how much more of this stuff is necessary? - inorder, parallel - foreach - generator,...

Should give a warning when there is a list of stateful tests not tagged with inorder, but assumed to be executed in order. This is an issue because the EUnit...

Ensure that files are dealt with properly - access both source and test files - look at module and module_tests