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
Chenguang Zhu created an issue 2018-01-30
Summary: Given a JUnit test that asserts the value of an instance field of a class, when changing the initialization of that field, Clover does not select the test to run (even when the initial value of the field is modified).
Steps to Reproduce: Run the bash script ./s provided in this directory. This script (1) runs the test class p.CTest with Clover, (2) changes the initialization of the field f in class C, and (3) runs p.CTest with Clover again.
Expected Results: p.CTest runs both times (it passes in the first run and fails in the second).
Actual Results: p.CTest runs only the first time (and does not run test the second time).
The text was updated successfully, but these errors were encountered:
Chenguang Zhu created an issue 2018-01-30
Summary: Given a JUnit test that asserts the value of an instance field of a class, when changing the initialization of that field, Clover does not select the test to run (even when the initial value of the field is modified).
Steps to Reproduce: Run the bash script ./s provided in this directory. This script (1) runs the test class p.CTest with Clover, (2) changes the initialization of the field f in class C, and (3) runs p.CTest with Clover again.
Expected Results: p.CTest runs both times (it passes in the first run and fails in the second).
Actual Results: p.CTest runs only the first time (and does not run test the second time).
The text was updated successfully, but these errors were encountered: