Feature #97
openAdd tests on the client's feature
10%
Description
So far, tests are only performed on the SharpScript engine, which is important but not sufficient. A lot of tests could be performed without the user interface being active. Some mocking would be required. These features should remain stable no matter the modification, and unittests are an excellent tool to ensure compatibility. It would be worth spending time puzzling over the mocking of the user interface as well, to ensure the main features remain always accessible no matter what.
Please register to edit this issue
Also available in: Atom PDF Tracking page