In one of the projects I am involved with, common functionality applies to various communication channels such as Sms, Email, Ad-words and Web banners. Naturally in a situation like this the question comes in mind is: "Do we repeat the test cases for every communication channel?" The answer I am always giving is: "It depends on the qualification method used".
For qualification methods such as Manual or Exploratory testing it’s a matter of time and manpower to execute as many times as our communication channels...
Tuesday, September 4, 2018
Tuesday, April 15, 2014
Having a multi tenant application under test, concurrency testing is the next step of the testing cycle. Testing using concurrent users takes a lot of time and usually ends up in defects not fully reproducible because of timing issues (synchronization) thus making automation of these tests a must.
Automating concurrent tests using selenium / webdriver always brings up one of the most common question in automation testing; Do I need a new window...
Friday, April 4, 2014
Lately, we've been using Stevia a lot; we're also extending it as much as possible (no promises, but phantomjs is in our crosshairs lately). By talking to the community, it has come to our attention that people are having difficulty to start up a Stevia project. To that extend, we've created some content to give you a boost:
Our SNAPSHOT javadoc is regularly published in Github Pages,
We've setup Travis continuous integration and our...
Wednesday, February 19, 2014
The Page Object design pattern is one of the most popular patterns in test automation just because it promotes test maintenance and unifies the way QA teams work. As the pattern dictates, a page object is the representation of an html page using objects. The objects contain the html element addresses (Xpath, Css or DOM) and the user actions on them as methods (press, input, select, etc.).
Although the page objects pattern is widely accepted, our...
Tuesday, February 11, 2014
When we finished the design of our objects for setting up
the preconditions of an automated test case we showed it to one of our
developers and his first reaction was “it is the same with the app’s domain
model”. This comment made me think that knowing the application internals would
be extremely useful in developing correct test scripts. Knowing this had me thinking that the gray box
testing would be more appropriate in our automation tests than black box, thus
a switch to that direction is worth considering.
Why is gray box more appropriate...
Tuesday, November 5, 2013
During the automation regression circles there are some defects that are carried over through the iterations.
So these tests appear as failed to ReportNG. Due to the fact that the new tests may introduce new defects that appear as failed to the report as well, some time is difficult and time consuming to distinguish between the old and the new defects.In this post we will describe a technique to illustrate the tests with the old defects in...
Tuesday, September 17, 2013
One of the most common tasks in our project is to retrieve data from a table in order to assert. With this post I will try to describe a unified way to get the required data from any table with a specific format so my assertions are well defined.
The assertion points to be well defined I usually prefer to have my actual data in the form of a Map(key,value) so my assertions are in the form
Assert.assertEquals(data.get(key),expected_value)
I selected the key value for my map to be the value of the first column with value a second map containing...
Subscribe to:
Posts (Atom)
