When a tester starts working on a new test task, the very first thing is to get to know the requirement (or User Story). This post shows how to import a user story from JIRA (widely used in project as the agile project management tool) into TestWise for creating an automated test quickly.
1. Here is a story card in JIRA
After creation, remember its ID, typically in a format PROJECT_ID-NUMBER, eg. CW-113
2. Set up JIRA integration in TestWise
3. Creating a new test, type story ID, e.g. [CW-113] in test case name, right click to select "JIRA: Show Issue #STORY_ID"
The story title will be shown in a "Requirement" panel.
4. To set the test case name for the story, click the button "User requirement as test case"
5. Click "Insert test steps" button will add the description in the story card into the test case as comments.
Another benefit of this, if this convention ("[STORY_ID] story name") is followed, later you can use StoryWise to generate Traceability Matrix.
However, these are just minors in test automation, don't get carried away with this. Focus on test script maintainability and test execution with CI.
"No.1 goal of CI at Facebook is developer efficiency"
"The system must provide frequent feedback to developers. Because the sooner we let them know about a problem, the easier and faster it is for them to fix it"
"At Facebook, We have some of our top engineers working on development infrastructure
"It is really important at Facebook I will never, as a developer, write code and toss over the fence and for someone else to write test for it. It is my job as a developer at Facebook to write tests for my code, and my reviewers make sure I do".
On Selenium WebDriver:
"For all of our end-to-end tests at Facebook we use WebDriver, WebDriver is an open-source JSON wired protocol, I encourage you all check it out if you haven't already. "
One of the great advantages of WebDriver is that it gets applications cross all platforms.
Several years ago at a conference, when I showed a stats of 200K+ test executions for a government project I led, I could sense doubts from audience. This week, the number of test executions conducted against my own application ClinicWise exceeds a quarter of a million.
This is achieved with the tools (TestWise, BuildWise Server + BuildWise Agent) and practices I covered in my book: "Practical Web Test Automation". And development and testing are all done in my spare time.
As the graph below shows, the number of automated tests grows with the development. People who had attempts with test automation will know, rare projects can achieve this.
The following graph shows automate testing keeps defect defects very early (typically within 10 minutes of checkin). To ClinicWise customers, the software is solid and nearly defect-free, at frequent (daily) deployments.
Every full build will run all UI test cases. The overall test execution time is dramatically reduced by distributing to multiple BuildWise agents to run in parallel.
Without these automated tests, ClinicWise simply won't be possible.
There are still commercial testing tool vendors trying to get you to purchase their expensive record-n-playback tools, but in my opinion, their days are numbered, Selenium WebDriver (or equivalent) is the way to go in the domain of testing web applications. Here are some hard facts:
Nowadays testing web applications on IE is not enough, as Chrome and Firefox are also the main stream browsers.
Google and Mozilla have been supporting Selenium WebDriver for a long time, and looks like Microsoft finally on board by releasing
IE WebDriver Tool for Internet Explorer 11. The chances for a proprietary testing from one commerical testing tool to get support from Mozilla, Google and Microsoftwre is very slim.
Support for multi-platforms
There are increasing number of IT professionals using Mac, and some want to run tests in free OSs such as Linux.
The demand for Selenium has already been reflect in the number of job ads. Based on
Indeed's job trend, Selenium has overtaken QTP (regarded as the long-time leading automated testing tool) in 2012. Since then, the number of QTP jobs nosedived.
Sometimes, testers want to use utlitiy gems in the test scripts. For example, aws-s3 gem can be used for checking the files stored in AWS S3. Thanks to the openness of TestWise, it is pretty easy to do.
Let TestWise know the new gems
Open c:\agileway\TestWise\Gemfile in a text editor, and add your gems there.
Install the new gems
In a command window, run these 3 commands.
Please note that incorrect customization of an TestWise installation may result in TestWise failing to start, and AgileWay unable to support it.
"Engineering teams have traditionally been split between program managers, developers and testers. Yet with new cloud methods of building software, it often makes sense to have the developers test and fix bugs instead of a separate team of testers, Nadella said in an interview last week after unveiling his memo."
"Some of the cuts will be among software testers,"
In Australia, we still call people perform software testing "Testers". As we know from the book "How Google Tests Software", it is called "Software Engineer in Test" (SET) at Google. When I was in America last year, I saw many "SET" job ads on STARWEST conference.
Today, following a link from LinkedIn Update email, I was quite shocked that how quickly and big the change is: The number of SETs jobs are 10 times more than software testers