TEST THE RISK!

Integration testing has an important role in the test pyramid, it aims to test the integrations of the software products in the integration environments. This means that the software should be built and deployed to an integration test environment and then run the test against the version in the testing environment. If anything wrong occurs as a regression issue then the CI gives feedback about the failures. As a result, the issue should be fixed and built and deployed to the integration test environment. Therefore this process is very expensive and is so late for the modern approach to SDLC, for the shift-left approach. As a solution to this problem, we should consider testing the integration isolatedly within the context of the software itself. Contract testing is an approach to testing the integration depending on the written contract during the build phase. In this post, I want to explain the importance of contract testing. What is Contract The contract is a document created by the

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.

Selenium and Watir Selenium and Watir are both open source and well-known automation tools. The power of Selenium is great but sometimes it may lead some insufficient result for executing test cases, or some difficulties can be achieved by Watir easily, surely or wise verse. Therefore we can use Selenium and Watir together for automating web applications. In this post, I want to show a sample to illustrate how to use both of them in the same automation framework. Possibly you maybe find something more accurate than what I did, fell free to post your thoughts. I have used Selenium with Pyhton as a base automation framework and call Watir in Ruby which Watir can be just only implemented by it. If you use another language than Python, you should use its features. In the sample, sign up for MYHABIT is implemented as Watir function in the name sign_up() and it is called by Selenium.  To call the Watir, Python module must import Popen, PIPE, STDOUT from Subprocess like as f