Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests and CI #115

Open
PurHur opened this issue Jul 15, 2019 · 2 comments
Open

Tests and CI #115

PurHur opened this issue Jul 15, 2019 · 2 comments

Comments

@PurHur
Copy link
Collaborator

PurHur commented Jul 15, 2019

The old behat tests for the behat formatter arent working anymore. The test tested the old HTML layout very hardcoded. Should we proceed like this?
Since we now can load different templates we could create a own simplified template just for the testing pipeline.

What do you think? @donkidd

@donkidd
Copy link
Collaborator

donkidd commented Jul 15, 2019

I think that is simple tests for that are fine, I was also thinking that we should probably have some tests out there to test the actual classes doing the work. So the behat tests seem like more end to end type tests that make sure that the entire plugin works. But should we also have some unit tests to test & validate the actual classes that are behind the entire plugin?

@PurHur
Copy link
Collaborator Author

PurHur commented Jul 15, 2019

Yes that should be tested too since i feel like there are some basic bugs in the basic Feature/Scenario classes. But the behat test would be a simple "it just works now" test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants