TestWorks Solutions

TestWorks Solutions

TestWorks products can be integrated into your quality assurance testing process in a variety of ways (see our TestWorks Quality Index). To help you get the best use from TestWorks we've outlined below some of the more-standard "prescriptions" that apply to common quality assurance and testing situations.

Your own situation is, of course, probably going to be different. Feel free to send us Email at info@soft.com and we will be pleased to assist.

E-Commerce
Solution
The TestWorks E-Commerce Solution includes our new test enabled web browser eValid eValid (Comments) operating along with SMARTS.
In addition, we have assembled a set of subscription-type eValid Test Services that apply our products in a 7x24 context.
TestWorks
Applied
To Y2K
Testing
We see the Y2K problem as composed of five separate steps. TestWorks can help with the last two (Confirmation/Testing and Verification).
Here are explanations of each of the five Y2K steps along with an approximate estimates of the proportion of total effort needed for that phase of the job. Note that the Confirmation/Testing and Verification phases often can account for up to 60% of the actual work!

Phase 1: Planning (5%)
Phase 2: Identification (10%)
Phase 3: Remediation (25%)
Phase 4: Confirmation/Testing (30%)
Phase 5: Verification (30%)
Integration Testing

What is integration testing good for?
What do I have to do to make TestWorks integrate into my software process smoothly?
Why do I have to keep my software maintenance current?
What if I have problems with TestWorks after 30 days?
Embedded and Cross-Testing

What does cross-testing mean?
Does TestWorks test embedded code?
How many changes to my code do I have to make for TestWorks to be effective?
My frequently asked question isn't answered above? What should I do?

Remote Testing
The Remote Testing Option (RTO) of TestWorks/Coverage gives you the ability to record test coverage data "from the field". This is an ideal way to gain details about how well your beta-test activity is proceeding.
RTO gives you the possibility of collecting coverage data on your product from a wide variety of users at very low overheads.
For What Languages is the RTO Option Available?
How does RTO work for Java??
How does RTO work for C/C++ and COBOL?

TestWorks
Applied To Y2K Testing `(TOP OF PAGE)`

We see the Y2K problem as composed of five separate steps. TestWorks can help with the last two (Confirmation/Testing and Verification).

Here are explanations of each of the five Y2K steps along with an approximate estimates of the proportion of total effort needed for that phase of the job. Note that the Confirmation/Testing and Verification phases often can account for up to 60% of the actual work!

Phase 1: Planning (5%): Figure out what to do and schedule resources to get the job done.
One can use much conventional program management tools -- and there are certainly plenty of them around! -- to carefully plan the work effort.
Phase 2: Identification (10%): Find the places in the code tree where instances of date dependence happen and ferret out what other parts of the code tree depend on these passages.
The tools here involve local syntactic and partial semantic analysis of the source code tree for specific date references, or date dependence references. This step need not be highly automated and most of the time you can use conventional tools you already have at hand. In other words, finding what to fix involves careful and rigorous use of the search functions on program editors combined with careful record-keeping. The main risk here is that a date reference or a date dependency that OUGHT to be remedied (modified) is missed.
Phase 3: Remediation (25%): Make the changes to the code tree to assure that the NEW software will not have the Y2K problem.
The programmers love this step and one hopes that the new passages of code are "better written and more clearly documented" than the ones being replaced. It is probably good practice to keep the "old code" present but commented out -- just as a reference.
Phase 4: Confirmation/Testing (30%): Confirm that the modifications are functioning properly.
The task here is to create a reproducible record that demonstrates that the modified program works correctly across the year-2000 boundary.
TestWorks helps with use of our regression products: creating tests that show how the remediated (modified) program works (using TestWorks/Regression's CAPBAK) and sets of tests are stashed in a test tree (using TestWorks/Regression's SMARTS).
Typically you will record and save tests of your Y2K compliant application for test scenarios that include the years 1999, 2000, and 2001. This helps confirm that the work of Phase 3 was successful.
Phase 5: Verification (30%): Verify that the tests used in Phase 4 really do exercise all of the modified code and, as well, that any code that depends on the modified code has also been covered by some dynamic test.
TestWorks helps there through application of TestWorks Coverage's TCAT coverage analyzers, available for C, C++, Ada, F77, COBOL, and Java.
The verification step's main value is to find out what you didn't test so that you can add additional cases to your test suite (in Phase 4). A good target is 90%+ C1 (branch coverage) if you want high confidence in the quality of the change.

Integration Testing `(TOP OF PAGE)`

What is integration testing good for?
Most of the time you put two or more pieces of a big system together after you've made sure they work separately. Doing this is called integration testing.
A lot of defects that can hurt you later get discovered in integration testing, and TestWorks helps by insisting on high levels of call-pair coverage during the integration test process.
What do I have to do to make TestWorks integrate into my software process smoothly?
First, make sure your software process runs smoothly in the first place. If it does, then TestWorks will add to the existing processes quite nicely.
Why do I have to keep my software maintenance current?
You gain two main things: continuous technical support, and you have the option of getting upgraded products at no cost.
Hint: Once your maintenance lapses it is more expensive to restore it than it would be if you maintained continuity. Normally you're in a "lapsed maintenance" state 60 days after the end of your prior maintenance.
What if I have problems with TestWorks after 30 days?
If you are not on maintenance, we will do our best to help. If you are on maintenance, we WILL help! This is a good reason to be on maintenance.

Embedded and Cross-Testing `(TOP OF PAGE)`

What does cross-testing mean?
If you're developing on one machine -- a host -- and you're product runs on another machine, that's called cross-development.
Cross-testing is TestWorks' way of supporting cross-development.
Does TestWorks test embedded code?
Indeed, for cross-development host/target type environments we have special kits you can obtain to help you test your embedded code. The kit contains the source of a compatible version of the runtime that you cross-compile to your target so that you can collect coverage data from the application as it runs there.
How many changes to my code do I have to make for TestWorks to be effective?
None.
The coverage analysis tools work with source code modification, but they make "throw away" versions of your code, then feed that directly to your compiler. You never [have to] see the intermediates.
My frequently asked question isn't answered above? What should I do?
Send your question to info@soft.com and we'll answer it immediately, and then add it to this page as soon as we can!

Remote Testing `(TOP OF PAGE)`

The Remote Testing Option (RTO) of TestWorks/Coverage gives you the ability to record test coverage data "from the field". This is an ideal way to gain details about how well your beta-test activity is proceeding.

RTO gives you the possibility of collecting coverage data on your product from a wide variety of users at very low overheads.

For What Languages is the RTO Option Available?
We can arrange for RTO support for C, C++, Java and COBOL.
How does RTO work for Java??
TestWorks RTO support is available for C/C++ and Java applications. You can try out the Java RTO capability on this website. The technology demonstrated collects coverage data from an instrumented Java application that runs on Java-enabled clients and reports coverage to our website. (We E-mail you the coverage report after the fact.)
How does RTO work for C/C++ and COBOL?
For C/C++ and Ada and COBOL applications, you provide your beta-site customers with an instrumented version of your application (the overheads are very low, e.g. 2%-5%) and after each use of the product the intermediate tracefile data is Emailed to your site for analysis.

E-Commerce Solution	The TestWorks E-Commerce Solution includes our new test enabled web browser eValid eValid (Comments) operating along with SMARTS. In addition, we have assembled a set of subscription-type eValid Test Services that apply our products in a 7x24 context.
TestWorks Applied To Y2K Testing	We see the Y2K problem as composed of five separate steps. TestWorks can help with the last two (Confirmation/Testing and Verification). Here are explanations of each of the five Y2K steps along with an approximate estimates of the proportion of total effort needed for that phase of the job. Note that the Confirmation/Testing and Verification phases often can account for up to 60% of the actual work! Phase 1: Planning (5%) Phase 2: Identification (10%) Phase 3: Remediation (25%) Phase 4: Confirmation/Testing (30%) Phase 5: Verification (30%)
Integration Testing	What is integration testing good for? What do I have to do to make TestWorks integrate into my software process smoothly? Why do I have to keep my software maintenance current? What if I have problems with TestWorks after 30 days?
Embedded and Cross-Testing	What does cross-testing mean? Does TestWorks test embedded code? How many changes to my code do I have to make for TestWorks to be effective? My frequently asked question isn't answered above? What should I do?
Remote Testing	The Remote Testing Option (RTO) of TestWorks/Coverage gives you the ability to record test coverage data "from the field". This is an ideal way to gain details about how well your beta-test activity is proceeding. RTO gives you the possibility of collecting coverage data on your product from a wide variety of users at very low overheads. For What Languages is the RTO Option Available? How does RTO work for Java?? How does RTO work for C/C++ and COBOL?

TestWorks Applied To Y2K Testing (TOP OF PAGE)

What is integration testing good for?

What do I have to do to make TestWorks integrate into my software process smoothly?

What does cross-testing mean?

For What Languages is the RTO Option Available?

TestWorks
Applied To Y2K Testing `(TOP OF PAGE)`