Software Testing
Finding the defects others miss
Problems we solve
Don’t let a critical software defect jeapordize your future!
Of course you Test ...
That you test your software is not the issue ...
• What you test
• Why you test it
• When you test it
• and How you test it
• Why you test it
• When you test it
• and How you test it
... makes all the difference between an expensive, marginally-effective process and an efficent, reliable way to find critical software defects.
Benefits
What can you expect if you hire us for your Software Testing? Things like:• Optimize your Testing costs with Efficient and Effective Test Plans and Methodologies
• Review and Develop complete, clear, accurate, and Repeatable Test Procedures
• Uncover the most expensive and pernicious faults
• Find defects in your software which traditional testing methods cannot detect
• Automate aspects of your testing process to reduce cost and test time
• Train your people to more effectively identify software errors – faster / cheaper / successfully!
• Review and Develop complete, clear, accurate, and Repeatable Test Procedures
• Uncover the most expensive and pernicious faults
• Find defects in your software which traditional testing methods cannot detect
• Automate aspects of your testing process to reduce cost and test time
• Train your people to more effectively identify software errors – faster / cheaper / successfully!
Software Test Services
Services which help our clients test effectively include:
• Test Plans and Procedures
• Real-Time Software Analysis
• Structured (White-Box) Testing
• Functional (Black-Box) Testing
• Code Inspections
• Custom Test Scripts
• Real-Time Software Analysis
• Structured (White-Box) Testing
• Functional (Black-Box) Testing
• Code Inspections
• Custom Test Scripts
Critical Analyses
“Industry Standard” testing cannot find some of the most critical defects: Race conditions, Re-entrancy clashes, Deadlocks, Timing problems, Stack Overflows, etc. These can be particularly problematic in Real-time Embedded Systems, whether or not they use an RTOS.We perform Critical Analyses on your code to uncover the defects which testing misses:
• Timing/Schedulability – will every task and interrupt always finish in time?
• Deadlock – how long could tasks block to wait for a shared resource?
• Stack Depth – can the stack overflow (or underflow) under worst-case conditions?
• Reentrancy – can a function/method be invoked safely by different priority tasks when necessary?
• Shared Resources / Race Conditions – are results affected by who calls the routine first?
• Deadlock – how long could tasks block to wait for a shared resource?
• Stack Depth – can the stack overflow (or underflow) under worst-case conditions?
• Reentrancy – can a function/method be invoked safely by different priority tasks when necessary?
• Shared Resources / Race Conditions – are results affected by who calls the routine first?