Good progress on the coding project today! \0/ Things accomplished:
- Added new test cases involving Categories, Tags, Pages, and Comments, to bring the total number of test cases up to 10
- Added the ability to run the cases via a Maven configuration as well as TestNG, and updated my pom.xml to use the testng.xml as its suite file
- Checked all the new test cases and related work into wp-test-demo-java
- Renamed my wordpress-dev repo to misc-configs, because that’s really what it’s for miscellaneous config files
- Updated my Postman collection to include all the endpoints for the test cases I wrote today, and checked the new version of that into misc-configs
- Updated the Readmes on both wp-test-demo-java and misc-configs to more clearly explain what the repos are for, particularly wp-test-demo-java, as I’ll be pointing recruiters at that
- Installed Jenkins (again) on my dev laptop, so that I can run the automation as a local Jenkins job as well as within IntelliJ, and to keep up my practice using Jenkins
I have decided, too, that I’ll be doing this project in phases.
Phase 1: REST API tests that hit the endpoints that can serve up publicly available data. I.e., the kinds of data you’d see as a user just browsing a WordPress site.
Phase 2: Selenium-based tests that will do front-end type tests. For example, “If I click on this link, does it take me to this expected target page?” Or, “If I click on this thing on the menu, do I get the correct dropdown off of it?”
Phase 3: This is the ambitious part. There are also REST API endpoints for WordPress that’ll let you get at the stuff you’d ONLY see as an authenticated user, such as post revisions and settings and the like. Time permitting, I may learn about the various ways to actually do that authentication properly so that the test suite can actually get at those endpoints.
Right now, though, I’m going to focus on phases 1 and 2.