Service Virtualization, Development Testing, API Testing Tips

March Mayhem Heats Up: Vote Now for Your Top Development Testing Practices and QA Strategies

Posted on Mar 26, 2015 10:54:56 AM

March Mayhem is coming to a head following two webinars discussing the value of the Eight Great testing activities.

Read More

Spring Shape Up: Trim Your IT "Waste" to Accelerate SDLC Velocity

Posted on Mar 25, 2015 6:45:44 AM

Now that Spring has sprung, there's no better time to revisit your new year's resolutions for  "waste" reduction.

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 weighty burdens such as the difficulty of 1) accessing complete Dev/Test environments; 2) acquiring complete, sanitized test data; and 3) configuring the behavior of the environment to enable complete test coverage. 

Fortunately, some strategic "spring cleaning" can help you make your SDLC leaner and more scalable.

Read More

Topics: Service Virtualization

How to Ease API Testing Constraints

Posted on Mar 19, 2015 6:08:19 AM

Ensuring API integrity is difficult in today's complex application cloud, on-premises and hybrid environment scenarios. In this interview with TechTarget, Parasoft solution architect manager Spencer Debrosse shares his experiences about the top API testing issues that organizations encounter and how automation and a DevOps team approach can address them.

The following is an excerpt from that interview...

What makes testing APIs challenging?

When you're building an application, you're not just using your own APIs or your own internal applications. Instead, you have to rely on a wide variety of endpoints and APIs and databases. We see lots of industry-specific, third-party API integration. For example, in the hospitality and airline industry, Sabre is common; in retail, credit card/address API verification is common.

If I integrate with Facebook or integrate with other applications, how can I tell if those APIs are in the state that I need them to be in, are available on my release schedule and are going to be functioning the way that I need?

That's really why availability's a constant problem, because we have all these pieces that are moving. Developers, as well as testers and QA architects, need to get all those pieces in sync to optimize their release schedule.


Read More

Topics: Service Virtualization, API Testing, API Integrity

March Mayhem Top 8 Testing Practices Announced

Posted on Mar 12, 2015 5:27:37 PM

The voting was fast and furious, but when it came down to choosing which testing activity provides the best value, the peoples’ voices were heard. We’re hosting a series of webinars beginning on March 19 to narrow March Mayhem down to the top development testing practice versus the top QA activity. You’ll only need to register once for all March Mayhem webinars: Sign up for all March Mayhem webinars

Read More

For Pi Day: How PIE Attracts Bugs (in your code)

Posted on Mar 12, 2015 9:30:00 AM

If you're like most software development teams today, you're now expected to deliver more software, faster. Many teams respond to this pressure by applying numerous automated test and analysis tools in conjunction with continuous integration. However, this tends to produce an overwhelming amount of data.

Read More

Topics: Development Testing

New Article: DevOps, Continuous Testing, and Service Virtualization

Posted on Mar 5, 2015 5:18:00 AM

Bob Aiello, Technical Editor of CM Crossroads, recently wrote an article explaining why organizations embracing DevOps and Continuous Delivery can't afford to move forward without Continuous Testing as well as Service Virtualization, which makes Continuous Testing possible.  

The following is an excerpt from the complete article...


DevOps provides a set of principles and practices which enable development and operations teams to communicate and collaborate more effectively. High performance teams which embrace DevOps have been demonstrating that they can deliver quality systems with amazing speed and agility. Many DevOps teams focus on scripting the application build, package and deployment process, resulting in an automated framework, known as the deployment pipeline. Deployment automation enables the organization to enjoy the benefits of continuous integration and continuous delivery, significantly enhancing productivity and agility.

Nevertheless, improving any process—from software development to manufacturing—inevitably involves an apparent trade-off between speed and quality. Understanding opportunities for acceleration is key for process improvement. Yet, speeding up the process without understanding the impact to quality opens up a distinct risk. In the same vein, organizations that are looking to accelerate their software delivery cycle need to ensure that the DevOps initiative is balanced with achieving the organization's definition of quality.

Read More

Topics: Service Virtualization, continuous testing

Software Development Testing and QA Strategies to Compete in Parasoft March Mayhem

Posted on Feb 26, 2015 11:38:00 AM

While the sporting world may be preparing for a certain college basketball tournament, we’re preparing for a bout of month-long madness of our own.

Next month, we’re kicking of March Mayhem: four weeks of all the crucial software testing information you can handle, culminating in a showdown between the top development testing strategy versus the top QA activity.

Before we can fill out our March Mayhem bracket, we need to narrow down the tournament to the Great Eight activities. Visit our survey page to vote for your top software quality strategy—the one that you and your team could not live without. 

Your Guide to the Championship Contenders for "Top Software Development Testing and QA Strategies"

Not sure which practice you want to champion? This guide provides a brief overview:

Development Testing Conference 

  • Static analysis: Compare your code to known best practices. Static analysis tools report a violation when your code deviates from safe, secure, and reliable constructions. This helps you expose defects and help prevent future defects with minimal disruption.

  • Unit testing: Verify that the code does what it’s supposed to do. Tests can be saved and reused as part of a regression test suite. Some level of test maintenance is required.

  • Coverage analysis: This technique tells you how much of your code is actually tested when you run your test suite. Coverage analysis is a requirement for safety-critical applications, but has value way beyond cars, insulin pumps, and airplanes.

Read More

Continuous Delivery…of Faulty Software?

Posted on Feb 19, 2015 7:41:15 AM

With the need for speed driving continuous integration, continuous delivery, and continuous release, organizations across industries are experiencing a rising rate of regressions, integration errors, and other defects. Accelerated delivery is great—unless you end up placing the business at risk because your testing efforts just can't keep pace.

Watch the on-demand How to Avoid Continuously Delivering Faulty Software webinar (co-hosted by Perforce and Parasoftto explore best practices for reducing the risks associated with Continuous Delivery. The webinar covers:

  • The top 4 best practices for Continuous Delivery.

  • The role that "DevTest" practices like static analysis, unit testing, functional testing, exploratory testing, performance testing, and security testing play in a Continuous Delivery process.

  • How to more accurately answer the core questions that different team members have (Development Manager, Architect, DevOps, Developers, Testers).

Read More

Topics: Development Testing, continuous testing

Top 3 Reasons to Love Automated API Testing

Posted on Feb 13, 2015 8:23:00 AM

APIs and the "API Economy" are currently experiencing an outpouring of love from developers and industry experts alike, but it's just not trickling down to API Testing.

If we want to to ensure that the business-critical APIs which are now so near and dear to our organizations are truly secure, reliable and scalable, it's time to start showering API testing with a little more love and affection. After all, API testing tools can provide some rather endearing benefits:

  • Reduced develpment and testing costs
  • Reduced risks
  • Improved efficiency


1. API Testing Tools Reduce Development and Testing Costs

API Testing tools drive cost reduction though:

  • Reducing testing costs
  • Lowering the amount of  technical debt you're accruing
  • Helping you eliminate defects when its easier, faster, and cheaper to do so

Reduced Testing Costs

Without an API testing solution, an organization’s API testing efforts predominantly involve manual testing plus limited automation fueled by home-grown scripts/tools and a motley assortment of open source or COTS testing tools. Having an integrated API testing solution not only dramatically reduces the resources required to define, update, and execute the prescribed test plan. It also enables less experienced, less technical resources to perform complex testing.

Testing costs can be reduced as follows:

  • Reduce outsourced (consultants/contractors) testing costs
  • Reduce internal testing costs

Reduced Technical Debt

Technical debt refers to the eventual costs incurred when software is allowed to be poorly designed. For example, assume an organization failed to validate the performance of certain key application functionality before publishing its API. A year after deployment, API adoption skyrocketed and performance began to suffer. After diagnosing the issue, the organization learned that inefficiencies in the underlying architecture caused the problem. The result: what could have been a 2-week development task snowballed into a 4-month fiasco that stunted development on competitive differentiators.

API testing exposes poor design and vulnerabilities that will trigger reliability, security, and performance problems when the API is dropped “into the wild”. This helps organizations:

  • Reduce the cost of application changes

  • Increase revenues through quick responses to new opportunities and changing demands

Read More

Topics: API Testing, API Integrity

Why Leading Companies <3 Service Virtualization

Posted on Feb 11, 2015 7:27:52 AM

There are a lot of things to love about service virtualization. Just consider a few of the many exciting findings from voke's recently-released  service virtualization research:

  • 36% of respondents achieved a greater than 41% reduction in production defects
  • 46% achieved greater than 41% reduction in total defects
  • 20% achieved more than 2X the test coverage
  • 26% achieved an increase of 2X or greater of test execution rates
  • 34% achieved a decrease of 50% or greater in test cycle time
  • 40% achieved a decrease of 40% or greater in release cycle time 

These stats are quite impressive. But what's a love story without, well, a story?

Here are some great stories about why leading organizations across financial, retail, travel, communications, utilities, insurance, and other industries fell in love with service virtualization...

Why Staples Loves Service Virtualization

Staples is committed to making everything easy for its customers, but ensuring positive customer experiences on their eCommerce site is far from simple. Functional testers must contend with the high number of dependent systems, subsystems, and services that are required to complete almost any eCommerce transaction—but rarely available for dev/test purposes.

The Staples eCommerce functional testing team turned to service virtualization in hopes that it would enable them to more rapidly and more exhaustively test complex transactions across highly-distributed systems.  They found that with service virtualization, they could start testing earlier in each cycle and complete their test plans faster.

This was especially critical on parallel development projects, such as when the Retail, Warehouse, and eCommerce teams were all working on functionality related to online ordering with in-store pickup.  This was a complex project with a very aggressive timeline. Using service virtualization to simulate resources that were still being developed, each team's development and testing could move forward without waiting on the others. With the virtual assets, they could start integration testing much earlier than if they had to wait for all the dependent components to be completed. This helped them get everything running smoothly even before they integrated all the completed components. Ultimately, they not only completed the project on budget, but actually ended up deploying it two weeks early.

Read More

Topics: Service Virtualization

Subscribe to Email Updates

Service Virtualization Best Practices


8 industry experts share insights & best practices about service virtualization and DevOps, Agile, cloud, performance testing, functional testing, API testing, business strategy, and more.

Follow Me