You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary: If one uses @RunWith(Suite.class), dependencies do not
include code under test (or test classes that are in the suite). This
is a safety issue, i.e., STARTS may not select a test with changed
behavior.
Steps to Reproduce: Unzip the attached file. Run the bash
script ./s provided in this directory. This script first runs test with
STARTS, then change the return value of a method under test,
finally runs the same test with STARTS again.
Expected Results: p.RegressionTest runs in both the first and the
second execution. It passes in the first execuion, and it fails in
the second execution.
Actual Results: p.RegressionTest runs only in the first execution.
The test is not selected in the second execution.
@Chenguang-Zhu, thanks for reporting! Preliminary investigation shows that the problem is not about @RunWith(Suite.class), but rather, ClassTest0.class is not a compile-time dependency of p.RegressionTest. Here's the jdeps output for p.RegressionTest:
Summary: If one uses @RunWith(Suite.class), dependencies do not
include code under test (or test classes that are in the suite). This
is a safety issue, i.e., STARTS may not select a test with changed
behavior.
Steps to Reproduce: Unzip the attached file. Run the bash
script ./s provided in this directory. This script first runs test with
STARTS, then change the return value of a method under test,
finally runs the same test with STARTS again.
Expected Results: p.RegressionTest runs in both the first and the
second execution. It passes in the first execuion, and it fails in
the second execution.
Actual Results: p.RegressionTest runs only in the first execution.
The test is not selected in the second execution.
starts_bug_test_suite.zip
The text was updated successfully, but these errors were encountered: