The following features were introduced or enhanced in StormRunner: UI Enhancements: New UI layout that includes breadcrumbs for easy test navigation. Duplicate the definition of an existing test to a new test. An enhanced Reports page layout includes new metrics and an easy navigation bar. In the Dashboard, you can sort column values in the widget summary view.
Published in Mobile Testing
JIRA – Agile Project Agile methodology for software development has gained immense popularity in the recent years. Agile Projects follow an incremental approach to development of the requirements. The highlights of an Agile/Scrum Project are: The requirements are created/agreed upon and the grouped together into a Product Backlog The requirements (User stories) are ranked in the order of priority and business importance Once ranked, the stories are assigned developmental cycles (Sprints) that last for approx. 4-6 weeks. The detailed documentation is avoided. Instead, a scrum board is maintained that will show the status and progress. JIRA successfully supports all the activities listed above for projects following an Agile Methodology. In this article, we will see how. Note – Firstly, you will need JIRA Agile add-on if you have not gotten it already.
JIRA Administration: We are going to learn all about JIRA administration today. This is a unique opportunity to learn the admin aspects of a Project/Incident/Test Management tool. This is the 5th tutorial in our JIRA learning series. Check all the tutorials in this series on this JIRA Tutorials page. Not all of them are as effective (and simple) and as accessible from the UI as it is for JIRA. So, as always, concepts are more important than the tool specific details – look out for the operations and their importance- that will help you to estimate what you can expect from the “Admin” module of any tool.
JIRA User Module – Conclusion We have seen the different kinds of issues and how to create them in our previous JIRA Tutorials. This is a next JIRA tutorial in this series where we will learn how to use them, the workflow progress and the reporting feature of JIRA. The issue once created can be accessed by searching the ID, browsing the “Issues” menu item or going to the project details and checking the issues tab. When you access an issue and click on its link, the details will be displayed. All the actions that can be performed on the particular issue are available on the header of an issue details screen:
A sub-task is nothing but a division of a parent issue (task) into chunks of work that can be assigned and tracked individually. Example 1: A QA related example could be of the task of Test documentation. Test documentation by itself is an activity that might take a week to finish. Say, it involves the following aspects: Test plan documentation which takes 2 days. Test case documentation – 2 days, Test plan review – ½ day and Test case review – 1 day. Also assume that there are 2 resources. In this case we can create a JIRA issue of the type task for “Test documentation” and have the following four sub tasks under it: Test plan documentation – assigned to resource 1 Test case documentation – assigned to resource 2 Test plan review- assigned to resource 2 Test case review- assigned to resource 1 By doing so, it is easier to have a better insight into the progress task wise and resource wise by breaking a sizeable parent task into sub-tasks.
Working with JIRA issues JIRA – we are in the midst of self-learning this tool. In the last JIRA tutorial, we talked about the underlying JIRA process – the Incident Management and a few high-level details of the tool itself. Today we move on to yet another interesting topic – How are issues handled in JIRA? Before we get into more details let us reiterate what an issue is: An issue is anything that you would track to completion. Some examples specific to QA can be – a document to be created, a document to be reviewed, a bug or an environmental issue.
Before we get into what this tool is, how it can be used and who it is used by, I want to lay out some ground rules that will help us learn any tool easily and effectively in a short period of time. I personally think that learning any tool has 2 phases to it: Understanding the underlying process Learning the tool itself- features/capabilities/shortcomings etc. Take the case of JIRA. Think that you are a newbie and know nothing about it. You have heard about it from various friends, online references etc. You want to try your hand at it. How can you do that?
We can easily run performance tests against Soap/Rest web services by using JMeter. REST web services uses the HTTP request method with most popular protocols like : GET and POST. The responses return status codes indicating success or failure, along with any applicable headers, and JSON representing the affected fields (or nothing) in the message-body. In this example below, we use OpenWeatherApi for web service test. For detailed information for the api, please visit the site: http://openweathermap.org/api
The Apache JMeter™ desktop application is open source software, a 100% pure Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions. In this example, you learn how to use Selenium WebDriver with JMeter to test performance of a web application. This example uses Mahara ePortfolio system as an example. We test the application's login and logout performance. To use Selenium Webdriver with JMeter, simply install "WebDriver Set" plugins. The WebDriver sampler is very useful if you want to test for performance AJAX, GWT based web applications and simulated user actions.