Service Virtualization, Development Testing, API Testing Tips

[Infographic] Evolving from Automated to Continuous Testing for DevOps

Posted on Jul 2, 2015 9:30:00 AM

The evolution of agile or lean development practices such as DevOps has come from businesses demanding more differentiable software. With this need for speed, we cannot assume that yesterday’s practices can meet today’s demands. Moreover, there needs to be a cultural shift from testing an application to mitigating business risks. That remains a gap in most organizations today.

Speeding up any process or system exposes constraints within the workflow. This will certainly be the case for software quality. If testing was traditionally a time-boxed event, accelerating the software release cycle merely compresses the time originally allotted for testing. If increasing the release cadence is the desired outcome, the software quality process needs to be re-engineered.


Read More

Topics: continuous testing

Gartner: DevOps Requires "Continuous Quality"

Posted on Jun 25, 2015 8:36:00 AM

Why Agile Development Teams Must Reinvent the Software Testing Process

In today’s economy, businesses create a competitive edge through software and every company is essentially a software company. Now that rapid delivery of differentiable software has become a business imperative, software development teams are scrambling to keep up. In response to increased demand, they are seeking new ways to accelerate their release cycles—driving the adoption of agile or lean development practices such as DevOps. Yet, based on the number of software failures now making headlines on a daily basis, it's evident that speeding up the SDLC opens the door to severe repercussions.

Organizations are remiss to assume that yesterday’s practices can meet today’s process demands. There needs to be a cultural shift from testing an application to understanding the risks associated with a release candidate. Such a shift requires moving beyond the traditional "bottom-up" approach to testing, which focuses on adding incremental tests for new functionality. While this will always be required, it's equally important to adopt a top-down approach to mitigating business risks. This means that organizations must defend the user experience with the most likely use cases in the context of non-functional requirements—continuously.

Read More

Topics: continuous testing

Automated API Testing Helps the Netherlands Secure a Nationwide ID System

Posted on Jun 18, 2015 7:39:00 AM

The Netherlands recently rolled out a new personal identification system, dubbed the Citizen Service Number (CSN), on a nationwide basis. The CSN is used by health care organizations, governmental entities and immigration officials to ensure proper identification and enable the provision of relevant services.

Considering the importance of this advanced system to the welfare and support of all citizens, the Dutch Ministry of Internal Affairs, which was responsible for its roll out, focused on ensuring that the system’s performance was exceedingly high. Fortunately, the ministry was able to meet its ambitious objectives within a demanding time frame. 

Using the top-ranked functional test automation / API testing tool, the organization reduced testing time for new releases of CSN from three weeks to just one day. This enabled the ministry to accelerate the project’s completion while maintaining top levels of software quality. Through regression and load testing, the organization has certified the system’s ability to handle 100 million transactions a year with a peak load of 200 transactions per second.

Read More

Topics: API Testing, API Integrity

Static Analysis Maturity Model: How Mature is Your Static Analysis Process?

Posted on Jun 11, 2015 8:20:41 AM

Learn Where You Stand Today and How to Reach the Optimized Level of Static Analysis

Static analysis is a quick and efficient development testing activity for preventing defects from impacting your applications. Every organization can benefit from static analysis, but implementing the activity without a strategy can limit its effectiveness.

The Static Analysis Maturity Model describes how organizations can best implement static analysis to maximize its benefits, which include:

  • Preventing defects that would consume exponentially more resources to remediate later in the development process.

  • Reducing risks associated with faulty software, which may result in costly litigation, brand erosion, or even loss of life

  • Achieving compliance with applicable coding standards to meet regulatory objectives.

Static analysis adoption can range from very simple ad-hoc or reactive efforts to mature efforts that are driven by corporate policies and leverage automated quality gates.

Read More

Topics: Static Analysis, Static Code Analysis, Development Testing

How Static Analysis Helped United Guaranty Reduce Application Risks and Cut Testing Costs

Posted on Jun 4, 2015 8:46:00 AM

When United Guaranty needed to re-engineer its core applications and infrastructure to achieve a business model transition, they found their existing development processes were insufficient for the new demands. Critical software errors were not being found through the existing quality assurance processes. Initial deployed versions of the applications contained errors, such as connection leaks, that caused the applications to sporadically become unavailabledisrupting the business operations that depended on them.

Read More

Topics: Static Analysis, Static Code Analysis, Development Testing

Evaluating Service Virtualization Tools? 43 Questions to Ask

Posted on May 28, 2015 7:41:00 AM

Move Beyond the Marketing Hype by Asking These Questions

Since service virtualization tools become part of your core architecture, selecting the vendor and product that's the best fit for your organization's process and culture is crucial to your long-term success and return on investment.

The vendor that's most prominent in the marketplace may or may not deliver the best results in your environment…but how can you determine this before you've already committed considerable resources to the initiative?

As you begin your service virtualization tool comparison, be sure to ask each service virtualization tool vendor a broad array of questions that will help you gain a clear understanding of their approach to service virtualization—and how that will impact your organization's productivity, costs, and success if you ultimately commit to working with this vendor.

With diligent probing, you'll be able to zero in on red flags related to:

Read More

Topics: Service Virtualization

Service Virtualization, API Testing Webinar with Forrester and Alaska Airlines

Posted on May 18, 2015 8:18:00 AM

Why Testers Can't Test: Solving the Test Environment Dilemma

The business demand for "more innovative software, faster" is driving a surge of interest in DevOps, Agile and Lean software development practices. However, today's testing processes are typically bogged down by the difficulty of
  • Accessing complete Dev/Test environments—including all system dependencies.

  • Acquiring complete, sanitized test data.

  • Continuously executing the tests needed to ensure a positive end-user experience.

Join Forrester's Diego Lo Giudice and Alaska Airlines' Ryan Papineau this Thursday (May 21) for the webinar Why Testers Can't Test: Solving the Test Environment Dilemma. The speakers will explore how leveraging advanced simulation for development and test helps leading organizations meet business demands while reducing risks.

  • Take a deep dive into Forrester's latest research on service virtualization and advanced automated testing.

  • Learn Alaska Airlines' best practices for managing the complexity of multiple dependent systems for testing.

  • Hear about how Alaska Airlines leveraged service virtualization to address common testing challenges.

  • Get Forrester's insights on why API testing is now essential for modern application delivery—and predictions for the future of API testing.

Read More

Topics: Service Virtualization, API Testing, API Integrity

What Do Software Defects Really Cost? The $2.3 Billion Bug

Posted on May 14, 2015 8:25:59 AM

Software development teams are scrambling to keep up with today's relentless demand for more innovative software—faster. Most are exploring new ways to accelerate release cycles (agile, lean DevOps..). Yet, based on the number of software failures now making headlines on a daily basis, it's evident that simply speeding up existing processes isn't doing the trick. 

How can software development professionals respond to this need for speed without increasing the risk of costly defects? That was the topic of Wayne Ariola's What Do Defects Really Cost? Much More Than You Think session at StarEast last week. Ariola revealed his research on the true cost of software defects—and why a new approach to testing/QA is required if you don't want to be responsible for a software failure that lands your organization in the headlines.

The following synopsis of that session was written by Noel Wurst, Managing Editor at Skytap, the leading provider of on-demand Environments as a Service (EaaS). It was originally published on the Skytap Blog...

Passive Quality Culture Leads to “Ticker Shock”

Asking a roomful of software testers, “What do defects really cost?” and then telling them, “much more than you think,” before anyone got the chance to answer is a pretty gutsy move. It’s certainly one that could’ve easily backfired for Parasoft chief strategy officer Wayne Ariola at last week’s STAREAST conference.

It did not backfire, and after waves of evidence of the immense financial impact that defects in production can have on an enterprise, I got the feeling that many in the room made mental notes to have some very serious conversations with various departments upon returning home.

Read More

Topics: continuous testing

How Automated API Testing Saved a NZ Bank $2.1 million

Posted on May 7, 2015 8:12:28 AM

To reduce the risks associated with their business-critical transactions, a leading New Zealand bank and financial-services provider wanted to extend their existing GUI-based testing to more extensively exercise the application logic within internal systems.

This logic resides within their ESB: a message broker component that features 80+ services and 750+ operations. The ESB represents a single point of failure within the infrastructure—but the company was unable to test it directly or automatically.

With the expertise of Parasoft partner IntegrationQA and Parasoft's market-leading API Testing solution, the company gained a service testing methodology supported by automated, reusable tests that performed a broad scope of testing directly from the service/API layer.

The result: they saved over $2.1 million NZD in testing and development costs over an 18 month period.


The Challenge: Ensuring that Application Logic Continuously Satisfies Expectations for High Reliability

The company's existing functional testing process provided some degree of black-box testing for the integration points between front-end and back-end systems. However, the company feared that this approach of relying on the front-end as the sole entry point for testing new functionality, technology updates, and large-scale changes to the existing infrastructure was not deep and rigorous enough to ensure that the application logic continuously satisfied the company's high reliability standards.

To reduce their risk exposure, they wanted to extend their existing end-to-end test scenarios to include direct and extensive testing of the ESB and associated services. However, they lacked access to the domain expertise and technology required to take their existing testing process to this level.

Read More

Topics: API Testing, API Integrity

API Testing Survey

Posted on May 1, 2015 7:39:46 AM

With the recent explosion of APIs and attention paid to the "API Economy", more and more development teams are finding that testing their enterprise and mobile applications now requires some level of API testing. But what level of API testing is actually being performed? And is the status quo achieving the expected results? 

Read More

Topics: API Testing, API Integrity

Subscribe to Email Updates

New Gartner DevOps Research


Read DevOps Requires “Continuous Quality” for the latest research on why and how Agile teams need to reinvent the software testing process.

Follow Me