Solution for Entegration of SpiraTest and Jira

SpiraTest is cheap but powerful test management tool. It has many useful features such integration to many open source and licensed testing and issue management tools, or automation host for HP QTP, IBM Rational Functional Tester, Selenium, TestComplete, the full list can be found here. Also it has requirement management, defect management, and there is a cycle for release - test set - test case - test run, and more can be found here. Jira is also well-known issue tracking tool and it used by many organisations. By Jira, you can track and follow the work items and easily manage the works. However it doesn't have basic testing activities so if you want to create test cases and manage the testing cycle Jira is not yet enough for these activities. Using both of the tools, SpiraTest as test management tool, and Jira, as issue tracking tool, may lead some difficulties such as raising defect from SpiraTest and creating a related issue for development in Jira requires manual efforts. Integration SpiraTest and Jira can reduce the manual effort. You can reach the integration document from the Inflectra website which is the producer of SpiraTest. In this post, I just want to clarify some difficulties.

Firstly integration does many thing but not everything. Belong to customer support of the SpiraTest, integration does the followings:

- Adds new incidents from SpiraTest > JIRA
- Adds new issues from JIRA > SpiraTest
- Updates existing issues changed in JIRA > SpiraTest

As a result, it doesn't update the changes entered from SpiraTest to Jira. So once you update an incident from SpiraTest, the same update should be made in Jira too. Even this issue, integration is still very successful solution.

Second, in Jira project, if you have custom fields you must create custom fields respectively in SpiraTest to sync every fields. Then map the custom fields with the custom variable in Jira correctly. However, if you use SpiraTest version 4.0 and Jira version 4.2 you must use component id instead of component value.

Component Mapping

Otherwise it gives the following error:

05.06.2013 10:22	Error	Data Synchronization	Error Adding SpiraTest Incident to JIRA: com.atlassian.jira.rpc.exception.RemoteValidationException: {reporter=The reporter specified is not a user., components=Component/s is required.} : [] at System.Web.Services.Protocols.SoapHttpClientProtocol.Read	0	View Item
05.06.2013 10:22	Error	Data Synchronization	Error Adding SpiraTest Incident to JIRA: com.atlassian.jira.rpc.exception.RemoteValidationException: {components=Component/s is required.} : [] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse	0	View Item

Third, SpiraTest must know the users of Jira otherwise datasync gives warnings about unknown user to sync then discard the sync for updated issue. To solve the problem, both of the tools should use LDAP user list.

Last one, if you change trace logging parameters in the DataSyncService.exe.config file from "False" to "True", system event log gives more detail about the error in the system.

<setting name="TraceLogging" serializeAs="String">

<value>True</value>

</setting>

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last): File "D:\workspace\sample_project\sample_run.py", line 10, in <module> m.login() File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login driver.find_element_by_id("id_username").clear() File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each. This post is for Windows machines, if you are using Unix-like see this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby. Create scripts in a directory called scripts (in your home folder, like as ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py : Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part. The last part is related to asserting your test cases against to the

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients , hatch rate, running locust without web interface and there should be so

TEST THE RISK!

Search This Blog