Cloud-based load essay serviceBlazeMeterreleased a white paper that discussed continuous examine last week. The ‘ Continuous Testing ’ program leverage cloud and open source technology to bring better testing for DevOps and Agile drill enabling shorter freeing cycles with high lineament releases.

You might not normally consider back-end load testing as component of a continuous delivery procedure, but we believe in try all the things. By pairing BlazeMeter ’ s service with Sauce Labs ’ readily usable test cloud used for functional and unit testing and others such as performance screen with New Relic, users get access to a total spectrum of tests that help ensure the utmost coating quality- and that ’ s a big win for everyone.

To learn more about this continuous testing solution:

• See BlazeMeter & # x27; sContinuous Testing video in activity

• Download BlazeMeter & # x27; sContinuous Testing white paper

• Attend the Sauce Labs and BlazeMeterjoint webinar, February 24, 2015

For more information about BlazeMeter & # x27; s raw offering, see below - or read the total press freeinghere.

Now, screen can be make in a matter of hours, not days, eliminating clash and human error, and allowing teams to straightaway identify and direct any problems.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Continuous screen as a service using BlazeMeter & # x27; s testing platform, as good as industry standard tools and services such as Sauce Labs, Jenkins, GitHub and New Relic, employ the measure adumbrate below. Together with Sauce Labs, the two company provide a complete continuous prove as a service solvent for the integral testing lifecycle based on open rootage package and cloud based services.

Testing starts by the developer using BlazeMeter and/or Sauce Labs to evolve a comprehensive set of performance and functional test that wholly validate the lineament of the developed module. This set of tests will be used in later stages to proceed the validation of the module in the uninterrupted bringing process.

Tools, Scripting and Overall Test CreationBlazeMeter & # x27; s execution and Sauce Labs & # x27; functional examination platforms support reading scripts and running exam with & # x27; DevOps & # x27; friendly leading unfastened source tools (e.g. JMeter, Selenium) and languages, such as Python, Ruby, or still Shell Scripts. The testing solutions provide libraries and APIs to create & quot; homegrown & quot; trial utilise common DSLs. With the new continuous quiz service, the test creation and the running of the tryout can be done with a full-bodied API – everything can be automated disregarding of the scheme you are using. Additionally, developers can supplant scripts and use industry standard JSON files that all developers are familiar with, to configure the load test. This reduces the developer & # x27; s need to learn a new language and allows them to perform tests lots more quickly. Ideally, examination scenario and accompanying trial codes are pulled directly from a source control tool such as GitHub.

Provisioning & amp; ResourcesA set of tests can be run with different provisioning. For example, a developer can run a module test from behind the firewall with local resources. On production, the same test can come from multi-geographies from the public cloud with or without load. When a test configuration is execute in an environs (e.g. Dev, CI, Pre-Prod, Post-Prod), it can easy borrow a different provisioning scheme. With BlazeMeter & # x27; s continuous examination as a service, users can now use the same tool and exam definitions across the plank, regardless of how they require to interact with the system. The company provides a individual common program regardless of how a user require to interface with it, while accommodating both GUI and API accession.

For an organisation to run all required tests in parallel with 0 clip to test, sufficient resource need to be allocated for all teams according to their use case. BlazeMeter & # x27; s continuous testing on any tryout form, as well as on-demand, using simple API calls and running in parallel supports:

• Unlimited resources in public clouds (e.g. GCE, AWS, Azure, HP, Rackspace, Joyent)

• Private Cloud

• Running in the developer & # x27; s local environment or information middle behind the firewall

ReportingBlazeMeter and Sauce Labs & # x27; testing surroundings seamlessly integrate into existing reporting solutions such as Jenkins Performance Trend and existing standard open source and cloud-based tools in the continuous speech lifecycle. The combined solvent provide & quot; walk & quot; / & quot; fail & quot; drift reports and & quot; deep dive & quot; account for diagnostics and analysis. The testing solutions too overlay data from 3rd party systems such as New Relic to present a comprehensive picture.

Alerts In Case of FailuresThe testing environments can indicate a & quot; failure & quot;, gather all test artefact and immediately send them to the group of interested people (e.g. the developers). The solutions provide an alerting system per developer, module and project that allow running the exact failed examination all over again to identify the cause for failure.

Modules, Builds, Release Candidates, Releases and ProductionTaking a snapshot of a figure, release or production, provides different modules at different releases. To be able to comprehensively test every such snap, BlazeMeter can compound different test form fragments into one trial constellation. The continuous testing resolution now too granularly defines test result threshold with pass/fail results salve in XML formatting and consumed by JUnit.

Version Control Friendly Incremental TestingBlazeMeter & # x27; s continuous examination as a service framework is edition control favorable and supports incremental testing to associate test constellation, set of exam and examination with versions (e.g code, establish, RC, releases).

BlazeMeter & # x27; s Continuous Testing as a Service platform is immediately usable.