Closed lawrencegripper closed 3 years ago
Oh i'm just thinking of something wouldn't it be nice if we have tests for the examples?
If we have those users know how to write tests for their gocui programs and we can make our cd/ci stronger.
And can you add testing capabilities to the readme features section?
Yeah sounds good to me, I'll add a set of tests to one of the examples then reference to this from the docs showing how to run tests.
Playing around with how/what to expose, tests still look a bit busy so might add a few helper methods to make them nicer to write.
So I'm pretty happy with the way the tests have worked out (except I have a file called testing_test.go
and some of the naming).
Be great to get some thoughts on this before I write up the docs. The testing_test.go
should show how this can be used.
Any thoughts on this one? If we're happy with the approach I can finish off the docs and get this ready for review.
Think this should be all set, I've added some basic docs to the README and removed the usage of gomega
One last thing. Can you update to the latest master, after that I'll merge it :)
No worries, I've rebased this onto the current master
now.
Related issue
86
Describe
This is WIP looking at building a simple to use integration testing approach for gocui. The aim is to allow input and assertion about the resulting screen content.
Todo
[ ] Add some sample tests to the _examplesnot got time to complete this item atm.