Pharo Issue Tracker - Manuscript (Case [Issue]22233) SUnit - There is no class defining classNamesNotUnderTest in the system.

Manuscript Notification

	Marcus Denker edited Case 22233: There is no class defining classNamesNotUnderTest in the system.: Cleanup in SUnit: 1. Pharo Image • You are subscribed to this case

This seems to be part of the "Run Coverage" mechanism of the test runner. For coverage analysis one can add (for a test class) which package should be analysed (packageNamesUnderTest). Then classNamesNotUnderTest is there to *exclude* single classes from that.

To me that makes sense for a coverage tool. But the names are bad *and* it should be not in the Testrunner, but a tool on top.

The question is if we want to change that now...

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Later

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker