Hence, we can say it is the process of automating your code’s compile, static code analysis, documentation generation, etc for every single check in of code. The goal is to develop a robust build pipeline so that anything that breaks the pipeline is identified as fast as possible, because every single checked in change automatically leads to a complete run of the entire building pipeline. After having a successful CI for build, one can then make ‘build pipelines’ generating docs after a successful build, generating quality reports and maybe automatically deploying to/setting up test/production if one’s project have reach the expected quality and all unit, integration, smoke and qa tests pass. Ultimately, with its help we can  build our project and execute tests in a clean isolated environment each time one commit on CVS, with the help of a continuous build tool.

Share

The post Continuous Integration appeared first on Blog.

Initially Cucumber was implemented in Ruby and then extended to Java framework. Both the tools support native JUnit. Cucumber can be used along with Selenium, Watir, and Capybara etc. It supports many languages like java, Perl, PHP, Python, .Net etc.

One can use it more in different project environments., as it is very easy to learn and implement. One should apply BDD framework to API automation.The inbuilt runner for cucumber is JUnit but we can also use testng with it. BDD is most promising framework in industry because it shows interactions between a BA and automation engineer.  Cucumber is more like using COBOL. Write the tests in a more conventional programming language, like Ruby, Java, PHP, Python, C#, Haskell, Go, whatever. And Cucumber is not a testing tool. It is a tool to help non-technical people understand tests. If programmers are going to test a RESTful API, then they will achieve more by using a familiar programming language to write those tests.

Share

The post CucumberJS ( Tool on Behaviour Driven Development ) appeared first on Blog.

Every action and every conversion directly affects your bottom line and testing can help increase conversions in both major ways and minor ways that add up. While some people simply make a change and then track what happens in a live environment, why would you want to ever risk losing out on business or negative effects? Even the smallest changes should be tested and properly vetted if your goal is to have a site or app that is optimized for success. You simply won’t know the impact unless you test it. These are just general starting spots as depending on your business there could be quite a few more critical junction points that testing could help with. The bottom line is that testing can dramatically improve your ROI if you aren’t regularly doing it. Target audiences can be a complex group that might not always react or respond in the way you assume they will which is where testing comes in.

Share

The post Software Testing :: A Critical Approach appeared first on Blog.