I think it could be useful to allow a user to skip certain tests. Downstream projects might decide that they only want to implement a subset of the kernel interface, and it would be cool if they can still use the test runner for the functionality they have implemented.
Approaches like (repeated) --include and --exclude regex patterns that e.g. operates on methods (--exclude '.*_copy' --exclude '.*_transaction_.*') could be one solution, but I don't think it'd compose well with the chaining that the runner uses.
So, I don't think I have a solution, and I think it could be acceptable to decide that downstream simply must implement the entire spec, but at least it's worth discussing?
I think it could be useful to allow a user to skip certain tests. Downstream projects might decide that they only want to implement a subset of the kernel interface, and it would be cool if they can still use the test runner for the functionality they have implemented.
Approaches like (repeated)
--includeand--excluderegex patterns that e.g. operates on methods (--exclude '.*_copy' --exclude '.*_transaction_.*') could be one solution, but I don't think it'd compose well with the chaining that the runner uses.So, I don't think I have a solution, and I think it could be acceptable to decide that downstream simply must implement the entire spec, but at least it's worth discussing?