hvyindustries / skylift-public Goto Github PK

Running test classes/suites and even methods in parallel would significantly improve the performance of Skylift.

Code coverage will be generated per test thread, so as tests complete, their coverage can be updated.

The child process spawner is currently hardcoded for cmd.exe. This needs adapting to allow test runes on Linux and OSX

When I have two documents open side by side, code coverage for a test run is not updated in either unless I focus the document.

In rare cases the "test run in progress" indicator can continue running after a test run is finished. The only way to reset the UI is to restart VS Code.

Instead, we should force clear all timeouts when pausing test execution.

http://stackoverflow.com/questions/8860188/is-there-a-way-to-clear-all-time-outs#8860203

The more tests that fail because of a single line, the brighter the red of the line gets.

We should only assign the coverage marker once per line (updating it if necessary to indicate how many tests are failing)

Display code coverage over all code in your project to show which tests are covering each line.

Basic coverage (ie - covered or not) may be possible with PHPUnit's built in coverage, but this needs further investigation.

Currently we only display coverage for test methods (indicating pass/failure and risky/skipped/incomplete tests)