Add Sub-Tests for Builtins in Mandatory Tests #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces the ability to run specific sub-tests within the mandatory tests (m) for built-in commands (b). This provides more granular control over test execution, allowing students to focus on specific functionalities without running the entire suite.
Motivation:
Currently, running bash mstest m b executes all built-in tests. This can be time-consuming when focusing on a particular built-in command. The ability to specify sub-tests addresses this by allowing targeted testing, speeding up development and debugging.
Changes Proposed:
Documentation Update: The README file has been updated to describe the new sub-test functionality, including an example of how to use it with the echo builtin.
Script Modification: The core testing script (tester.sh) has been modified to parse and handle the sub-test argument. The case statement for "builtins" | "b" now includes logic to check for an additional argument and execute the corresponding test file.