Replies: 1 comment
-
I am def interested is a good way to test task files are working. I am hitting little bugs in task files that are hard to assert that they are not breaking. How best to do that I guess is an open debate. I like the idea of file based testing. The reason I say this is because I would like to be able to write tests for my own Taskfiles too. like here: https://github.com/joeblew999/pb-stack/tree/main/mod/_template/source-remote. Then I know the base task files are working for all the Developers and Users that use my base task files. And so do they :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Would there be any interest for a development of an E2E testing method using Testscript? Testscript is a different (but complementary) approach to the current unit tests, which makes it a easier to write tests which capture the user perspective (i.e. E2E tests). The Testscript package can also be extended, adding commands for specific cases (e.g. xpath like queries for yaml, or graph database queries).
An example testcase might look like this:
An E2E test suite is simply a collection of txtar files. They can be operated with
go test
. Adding support for Testscript based testcases in the Task repo would not be particularly difficult (it would slot in alongside cmd/task/task.go (as cmd/task/task_test.go).Beta Was this translation helpful? Give feedback.
All reactions