Channels ▼
RSS

Testing Cloud Apps Inside Workflow Comfort Zones


Mu Dynamics has pushed the integration of its Blitz application testing product onto multiple platforms including Heroku, AppHarbor, Acquia, and CloudFlare in an attempt to gain wider developer uptake. The integration has incorporated Mu's cloud-based load and performance testing technology, with a Platform-as-a-Service (PaaS) layer, a Content Management System (CMS), as well as web security and performance offerings.

The concept, on paper, is simple: App developers should be able to test the performance of cloud applications without leaving the workflow of their PaaS, CMS, or web management applications. Mu says that Blitz is specifically for the "fast-paced application" development market and has now been fully integrated into the PaaS providers most commonly used by application developers.

In related and more recent news, Mu also announced that Blitz has been integrated with the Atlassian development tool Bamboo, a Continuous Integration (CI) server. Atlassian has made Blitz available on its Plugin exchange.

According to Mu Dynamics, "Integrating Blitz and leveraging its cloud-based application load and performance service empowers Bamboo app developers to quickly and affordably identify the performance of their applications in real-time during the entire development and deployment process. This continuous performance management offered by the integration of Blitz and Bamboo guarantees app developers a better user experience for their customers."

By being incorporated into the Atlassian Bamboo CI server, Blitz now enables Bamboo developers to load and performance test their applications as a part of the continuous development and deployment process. Tests can be run the moment changes are checked in, ensuring those changes don't degrade performance. This seems to be emerging as an industry-wide best-practice approach to cloud app testing.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 


Video