| 1. | Is there a way to try Automated Testing Kit easily? |
Yes, follow the instructions at Applying the Automated Testing Kit Recipe. There will also be an opportunity to play with Automated Testing Kit at | |
| 2. | How is Automated Testing Kit different from the tests provided by Drupal CI (on Drupal.org)? |
There are two big differences. First, the tests in Automated Testing Kit will test the whole stack on any target you desire i.e. you get real-world feedback that a specific instance is working correctly. Start with a developer machine, move to a staging server and finally verify the production server (be careful with live data). Second, typically tests in the Kit are customized for the target site. For example, the included login test in Automated Testing Kit assumes a vanilla Drupal installation. However, during implementation the test typically is modified for the unique login needs of the site, which might have a different workflow (like Single Sign-On) or a different error display mechanism. | |
| 3. | Why wouldn't I just write these tests on my own? |
You certainly can but the point of Automated Testing Kit is to give developers a head start. We've thought through many of the issues you will face and include custom functions (such as Drupal hooks) that make targeting screen content easier. We have also thought through how to send Drush commands to a target server—even when the server is on Pantheon. You can use these tests to see how we accomplish certain tasks thereby make writing your own tests faster. (Have a better technique than we used? Join the #automated_testing_kit Slack channel and let us know!) On top of all that, we're always adding new tests and new helper functions. | |
| 4. | Can I upgrade from a previous version? |
Yes, but we expect that each team will modify the tests that are provided by Automated Testing Kit and commit them to their own repo. If you have done that, don't re-run the setup script or your existing tests will be overwritten. A new version will have more tests and more functionality as the test suite coverage increases. You can upgrade the Drupal module, the helper Javascript libraries and copy the new tests that you want to use. | |
| 5. | Are the tests available for XYZ framework? |
| We are committed to making the tests available in Cypress and Playwright for the time being. If you have re-written them in another framework (or want to), reach out on Slack and we'll discuss adding the tests to the project. |