behat-screenshot
behat-screenshot copied to clipboard
Symfony 6 support
Are there plans to add Symfony 6 support?
Short answer is no.
The long answer sounds like testing the UI from Behat is bad practice. First of all, such tests take much longer to write and run compared to utilizing your domain objects directly. Having the UI ready usually means end-to-end testing (preparing the database, running an HTTP server etc.) which is the slowest form of test feedback (See the Test Pyramid for more explanation.). Secondly, there are other tools designed specifically for UI testing which can do the job quicker and easier than PHP/Behat. So maintaining this extension further does not bring much value in my opinion.
Okay, thank you for the quick answer!
Hi @elvetemedve!
I completely agree about your reasoning regarding prioritizing unit testing over e2e testing. It is also completely understandable if you do not want to maintain this project anymore because you do not find it useful anymore. However, the statistics prove on Packagist that still package is still actively used: https://packagist.org/packages/bex/behat-screenshot/stats
I assume there is two way to move forward:
- looking for new maintainers who can keep maintaining this package
- giving up this package, marking this abandoned which will cause that somebody forks it and starts maintaining it
Btw, @tkotosz would like to still maintain this package?
P.S.: Frankly, we are also evaluating other alternatives for performing e2e tests for similar reasons that you have also mentioned. Although it does not mean that Behat and the existing tooling around it do not make it possible to use it for e2e testing also.
Hi @mxr576,
Well, since it's open source, contributions are welcome. But probably, I won't be able to react to PRs, issues, questions etc as quickly as an active maintainer would do.
So I agree with your observations.
Although it does not mean that Behat and the existing tooling around it do not make it possible to use it for e2e testing also.
Sure. It's up to the development team to make that decision and find the right tool for the job (if it's PHP and Behat, that's completely okay).