...
The Tapestry source includes several small web apps that are used by the automated Selenium integration tests. You can also run these apps manually to try out nearly every browser-visible aspect of Tapestry. Just invoke the corresponding Gradle tasks. This is mainly useful when debugging failing selenium tests.
- Command-line users:
- ./gradlew runTestApp1
- Eclipse users:
- Use the run-jetty-run plugin in Eclipse, with the context directory selected from among the
testcontext directories. For example, in the tapestry-core module, right click on the /src/test/app1 (or app2, etc) folder, and select Run As > Run Jetty, then open your browser to http://localhost:8080/tapestry-core
- Use the run-jetty-run plugin in Eclipse, with the context directory selected from among the
The "app1" app (the runTestApp1 tasks, above) is the one used by most of the integration tests. There are also app0, app2, app3, app4 and appfolder apps that can be run the same way.
Making Code Changes
Once you have cloned or pulled the latest changes to your local Git repository, you can start working on it. Whenever you make some changes to the codebase, it's good to have a related issue filed in JIRA and to use a similarly named branch in your local Git repository. For example, to create a branch for an issue with the key TAP5-123:
...