Tests #75

Open
opened 2024-02-28 07:14:07 +00:00 by emma · 6 comments
Owner

There should be tests for every utility. There should be no more new pull requests until there are tests for every utility currently in the tree. We can merge the existing ones and then make some tests for all of the utilities.

There should be tests for every utility. There should be no more new pull requests until there are tests for every utility currently in the tree. We can merge the existing ones and then make some tests for all of the utilities.
emma added the
enhancement
label 2024-02-28 07:14:07 +00:00
emma self-assigned this 2024-02-28 07:14:13 +00:00
trinity was assigned by emma 2024-02-28 07:14:13 +00:00
Owner

How should we do testing? I have a test.sh script I use for some of my own stuff - should we use that?

How should we do testing? I have a [test.sh](https://git.sr.ht/~trinity/src/tree/main/item/testing/test.sh) script I use for some of my own stuff - should we use that?
Owner

What do you think of TESTING?

What do you think of [TESTING](https://git.tebibyte.media/bonsai/coreutils/src/branch/testing/TESTING)?
Author
Owner

What do you think of TESTING?

This should definitely be in the tests/ directory to be directly run by the Makefile. Please name it something like tools-testing.sh to be consistent with posix-compat.sh. We can make note of the script in README but I don’t know if anything beyond make test is worth mentioning outside the comments in the script.

> What do you think of [TESTING](https://git.tebibyte.media/bonsai/coreutils/src/branch/testing/TESTING)? This should definitely be in the `tests/` directory to be directly run by the Makefile. Please name it something like `tools-testing.sh` to be consistent with `posix-compat.sh`. We can make note of the script in `README` but I don’t know if anything beyond `make test` is worth mentioning outside the comments in the script.
Author
Owner

Also, scripts should not be licensed under Creative Commons licenses, and the license information in non-plaintext files should be at the top.

Also, scripts should not be licensed under Creative Commons licenses, and the license information in non-plaintext files should be at the top.
Owner

What do you think of Testfile?

What do you think of [Testfile](https://git.tebibyte.media/bonsai/coreutils/src/branch/testing/Testfile)?
Owner

What if we just incorporated tests into the Makefile itself? So testing is done at build time and builds fail when tests fail. No Testfile, no TESTING, just additional testing lines in a build recipe to ensure everything works.

What if we just incorporated tests into the Makefile itself? So testing is done at build time and builds fail when tests fail. No Testfile, no TESTING, just additional testing lines in a build recipe to ensure everything works.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bonsai/coreutils#75
No description provided.