Project Update: First automated tests complete

New Tests

  • Accounts (2)
  • Homepage (1)
  • Blog (2)
  • Project (1)
  • Navigation Menu (1)

Notes:
I wanted to get a few basic tests in for each feature file I had planned out, then expand into more complex tests once these features were built out and working. So far things seem really basic, and even currently looking at the present features, it may not be complex enough for more sophisticated testing, so I may add more complex features simply for the sake of creating tests for them.

All of the tests for the Cucumber steps I’ve written are complete; some aren’t as versatile as I would like them to be so I will revisit them as I write more complex tests that need more versatility. What I mean by that is some steps are hard-coded towards specific areas instead of taking any passed variables from my Cucumber steps and using it to influence the step’s coding.

An example would be:

Given user clicks on “item”

Instead of taking the term listed in quoted in the Cucumber step, the WebDriver is coded to go to a specific xpath, so the step can only ever go one direction. I aim to adjust such steps to prevent repetitive coding.