-
Notifications
You must be signed in to change notification settings - Fork 271
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
[Question] Comprehensive Documentation #393
Comments
The documentation was originally included in the PHPUnit manual, but since then the package has been separated so PHPUnit won't have this documentation anymore. For new projects I usually go for Sphinx building documentation from text files in the But, I'm happy for suggestions about what is the easiest methods to keep that documentation alive in a form that is separated from the PHPUnit manual. |
We can do it also as a separate branch (gh-pages) but I'm not yet familiar on how to automate it; one of my to do to learn this 2017. Probably we can start the list of feature from the current version 3.0. We can layout the chapters, topics, etc. Thanks in advance. |
To be fair porting the existing chapter 13 (https://phpunit.de/manual/4.8/en/selenium.html) with its contents would already be a success. Then it can be reworked and expanded, but the problem to be solved is just to set up a process for documentation, not also to write it all at the same time. Speaking of 3.0, I would drop the |
Is there still no documentation? It’s hard to find information on how to use PHPUnit-Selenium. I wanted to add code coverage, I find messages mentioning a "coverageScriptUrl" var but without documentation it’s hard to understand how to use that. |
Hi @giorgiosironi ,
I would like to know is there a (updated) comprehensive documentation for this library? I know that it's included in the old PHPUnit branch (version 4.8) but currently it is not maintained in the https://www.phpunit.de site.
I would like to contribute and help with the documentation and updates of this library.
Thanks,
Gab
The text was updated successfully, but these errors were encountered: