This post is fourth of a series of nine. Need to go back to the beginning?
Drafting a Login Test for Amazon.com won't be as easy as drafting one for Dave Haeffner's mock site, The-Internet. There needs to be a lot more infrastructure put in place besides the CommonUtils library we worked on in the last blog post. Also, Amazon.com use the word "Login". Instead, they use the phrase Sign In.
December 31, 2015
December 28, 2015
Automate Amazon: CommonUtils, methods and exceptions
This post is third of a series of nine. Need to go back to the beginning?
The Selenium WebDriver API provides the basic methods to manipulate a browser to perform actions, such as navigating to a web page, but it doesn't have all the functionality we would need. What if we wanted to add in exception handling, such as if the web page was not found? What if we wanted to throw a customized error to a log file when the page was not found? What if, even upon a success, we wanted to write a message to the log?
A Common Utilities library, such as one they are using at my workplace, can be developed to handle these cases. Each Selenium API method is wrapped in try / catch / throw blocks for exception handling, built-in with logging functionality. When things go wrong, clear and concise error messages will save a lot of time debugging if the issue was with the server, with the code of the site, or the tests themselves.
The Selenium WebDriver API provides the basic methods to manipulate a browser to perform actions, such as navigating to a web page, but it doesn't have all the functionality we would need. What if we wanted to add in exception handling, such as if the web page was not found? What if we wanted to throw a customized error to a log file when the page was not found? What if, even upon a success, we wanted to write a message to the log?
A Common Utilities library, such as one they are using at my workplace, can be developed to handle these cases. Each Selenium API method is wrapped in try / catch / throw blocks for exception handling, built-in with logging functionality. When things go wrong, clear and concise error messages will save a lot of time debugging if the issue was with the server, with the code of the site, or the tests themselves.
December 24, 2015
Automate Amazon: Sketch out a Use Case
This post is second of a series of nine. Need to go back to the beginning?
With the last blog entry, we talked about setting up a development environment and running our first test.
With this entry, we are going to examine Amazon.com's site and see if we can come up with a quick test to automate creating a purchase order with Amazon's Sign In, AddToCart and Checkout process.
With the last blog entry, we talked about setting up a development environment and running our first test.
With this entry, we are going to examine Amazon.com's site and see if we can come up with a quick test to automate creating a purchase order with Amazon's Sign In, AddToCart and Checkout process.
December 22, 2015
Automate Amazon: Development Environment Setup
This post is first in a series of nine.
Back in June 2015, I blogged about how I would write automated tests vs Dave Haeffner's site, "The-Internet".
For this second project, I picked a more difficult site to automate: Puchasing an order on Amazon.com's site.
Back in June 2015, I blogged about how I would write automated tests vs Dave Haeffner's site, "The-Internet".
For this second project, I picked a more difficult site to automate: Puchasing an order on Amazon.com's site.
December 17, 2015
Next Week: Automating Amazon : How I Am Spending My Christmas Vacation
Automating Amazon: How I Am Spending My Christmas Vacation:
For the past few years, I have been coming up with little side projects during my Christmas break to help deepen my knowledge of the software testing industry.
- December 2012: Examining the book How Google Tests Software
- December 2013: Taking Alan Richardson's excellent online course Selenium 2 WebDriver with Java
- December 2014: I was quite busy! I retook Alan Richardson's course, spent time creating this blog, and I finally created a GitHub account storing Java and Python code samples I could show to prospective employers as I interviewed for automation development positions. Quite handy when I was caught up in a surprise layoff and was searching for automation positions this time last year.
December 16, 2015
New Editor's Draft of W3C WebDriver Specification Released!
A new Editor's Draft of the W3C Spec Has Been Published!
A new Editor's Draft written by Simon Stewart and David Burns has been released on December 3, 2015 to the World Wide Web Consortium's Browser Testing and Tools Working Group: https://w3c.github.io/webdriver/webdriver-spec.html
Subscribe to:
Posts (Atom)