[ALOY-636] Improved unit testing
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2013-06-03T21:31:13.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Titanium SDK, Tooling |
Labels | n/a |
Reporter | Tony Lukasavage |
Assignee | Tony Lukasavage |
Created | 2013-04-22T22:37:28.000+0000 |
Updated | 2014-01-28T23:19:50.000+0000 |
Description
Currently Alloy has coverage for all of its commands to various degrees. One area that could use more low-level unit tests is the compile command. Currently the compile command is tested by ensuring that all test apps are compiled correctly. This means that the result is not verified, only that it executed without error.
In order to better assess the stability of Alloy, we should be inspecting the results of the compile command to ensure that the generated code is as we would expect. This will involve testing the generated controllers as a whole, but will also include low-level testing of generated styles as well. This will make it much more likely that we are covering as much as we can with alloy.
Also, it wouldn't hurt to have another complex test app or two.
Duplicate of ALOY-651