Archive for August, 2009

Breaking Down the Walls

Monday, August 24th, 2009

There was a time in the semiconductor industry where the test assets created during the process were not re-used.  This meant that test engineers were forced to start from scratch each time they developed and implemented a test plan. To make matters worse, there was a giant wall between design and test teams.

There are a number of reasons why this wall was there but, for the most part, it persisted thanks to the very different ways in which design engineers and test engineers then approached their job. As a result, the way in which such accompanying technologies as simulators and programmable test equipment worked echoed the split between design and test. These differences were of course driven by the specific needs and focus of each test environment, a situation which resulted in test data being structured completely differently for designers than it was for testers.

To this day, this difference in mind-set and the way test data is represented persists, but the SemiCon industry has realized the value of design-to-test re-use and has found ways to bridge this gap. The result?  An entire support industry that specializes in technologies designed to convert test data from the formats used by design engineers to a format that can be used by test engineers. This conversion is often an extremely complex task, but tools and methodologies have evolved to the point where re-use of design test data by test engineers is the norm throughout the industry, and has resulted in dramatic savings in test engineering costs and reductions in time-to-market for products that are often characterized by an extremely small market window.  While the wall is still very much intact for now, the results seen here still represented a dramatic, positive shift in the way technology firms view the separation between design and test. As such, it should serve as an example for the high tech sector.

At SmarteSoft, we’re taking the lessons learned in the semiconductor industry and applying them to the wall that divides software development teams from the QA folks who test their applications. With such revolutionary products as SmarteStudio (look for a full release in September) and the forthcoming SmarteScript 6.0, our clients will find themselves suddenly able to integrate development and QA, cutting both costs and time to market, thus improving their ROI. In ten years this may well be the norm. For now, you can only find such revolutionary implementation here.

SmarteSoft Advantages Highlighted in Gartner Magic Quadrant

Monday, August 17th, 2009

On July 31st, Gartner issued its Magic Quadrant for Integrated Software Quality Suites report. In it, the firm — widely recognized as source for understanding corporate positioning in the tech industry — included SmarteSoft, characterizing us as a firm that has “been able to execute well initially, and has a good focus on building a complete platform for testing professionals.”

To read the full report please visit the Gartner homepage.

WSDL Automated Functional Testing with SmarteScript

Monday, August 10th, 2009

Web services have become an integral part of many websites and products we have been called on to test. Testing the functionality of the application is still the straight forward method that we propose in our standard training–even if web services may require a small amount of harness building.

Service oriented applications may have data which extends beyond the display layer, such as messages which initiate a new process or procedure. Testing those messages without a back end, code driven tool can present quite a challenge.

Most testers just want to get to testing, and would like to avoid generating an application which has to be re written each time the process or data changes. To facilitate this, SmarteSoft currently recommends creating a simple form that accesses the WSDL from the server.  This simple piece of HTML will provide for the inputs as well as the outputs.  As this service page is created it will allow for both functional testing of the web service, as well as load testing.