We have previously discussed adding resource-awareness to unittest, but that is a much bigger project (API design, scope considerations, etc etc). In the meantime, what we could do is modify the current resource-skip logic slightly: make it so that tests are *not* skipped for resource reasons *unless* some flag in support is set indicating that resource enforcement is in effect *and* the specified resource is not in the list of currently-asserted resources. That way tests are only skipped for resource reasons if run via regrtest.