The results of code coverage run can be seen at:
http://jfx.us.oracle.com/shared-webrev/almatvee/jpackage/jcov-report/windows/
for each method not called by running our tests we need to either:
1.) Identify that it is dead code and remove it.
2.) create a test that will cause it to be called
3.) Identify why it unreasonable to expect any test to call it.
This needs to be done for each file, the dead code removed, and new issues created for any additional automated tests required.
http://jfx.us.oracle.com/shared-webrev/almatvee/jpackage/jcov-report/windows/
for each method not called by running our tests we need to either:
1.) Identify that it is dead code and remove it.
2.) create a test that will cause it to be called
3.) Identify why it unreasonable to expect any test to call it.
This needs to be done for each file, the dead code removed, and new issues created for any additional automated tests required.
- relates to
-
JDK-8225428 CLI change to remove "mode", rename to "package", and build only one target
- Resolved
-
JDK-8224132 Investigate feasibility of doing SQE code coverage runs for jpackage
- Resolved
-
JDK-8226891 rename and re-layout jpackage tests.
- Resolved