Part of #3446. Phase 4 of eight.
Scope
test.dependent → org.testng.dependent
test.testng317 joins this phase. Phase 3 left it because it is about dependsOnMethods across
classes with matching names, not about the packages phase 3 owned.
That package needs a decision, not just a move. test.testng317.VerifyTest is in no suite file, so
it has never run. It also asserts nothing: it prints a method count and returns. Give it an
assertion and register it, or delete it.
How
docs/TEST_RELOCATION_PLAN.md holds the procedure and the phase table. Read the phase row there
rather than trusting counts written here.
Executable tests go to org.testng.<feature>. Classes handed to TestNG go to
org.testng.<feature>.samples. A class listed in testng.xml is executable; everything else is a
sample.
Done when
- Every issue reference in scope is proven, or removed.
docs/test-issue-references.md records what this phase verified.verifyTestExecution passes, and the execution inventory diff holds renames only.- The full build passes.
Part of #3446. Phase 4 of eight.
Scope
test.dependent→org.testng.dependenttest.testng317joins this phase. Phase 3 left it because it is aboutdependsOnMethodsacrossclasses with matching names, not about the packages phase 3 owned.
That package needs a decision, not just a move.
test.testng317.VerifyTestis in no suite file, soit has never run. It also asserts nothing: it prints a method count and returns. Give it an
assertion and register it, or delete it.
How
docs/TEST_RELOCATION_PLAN.mdholds the procedure and the phase table. Read the phase row thererather than trusting counts written here.
Executable tests go to
org.testng.<feature>. Classes handed to TestNG go toorg.testng.<feature>.samples. A class listed intestng.xmlis executable; everything else is asample.
Done when
docs/test-issue-references.mdrecords what this phase verified.verifyTestExecutionpasses, and the execution inventory diff holds renames only.