Static Analysis

Subscribe to Static Analysis: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get Static Analysis: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories

Parasoft's .TEST product aims to automate the creation and execution of testing for quality assurance of .NET code. Specifically, it can produce four kinds of tests: white box, black box, regression, and static analysis. White box tests are able to interact with the private members and variables in a software component to verify that it has been built properly. Black box tests, on the other hand, limit themselves to only the externally-visible portions of components, to verify that they interact properly with their environment. Regression testing occurs after all of the white boxes and black boxes have passed successfully for the first time. After this, every code modification should involve the repetition of all previous white and black box tests, to verify that no errors have been introduced by the modification(s). The final kind of testing that .TEST can automate ... (more)

SOA World - Exclusive Q&A with Dr Adam Kolawa, Co-founder & CEO of Parasoft

“Developers need to realize that Automated Defect Prevention benefits them," says Parasoft co-founder & CEO Dr Adam Kolawa in this Exclusive Q&A with SYS-CON Media's Java Developer's Journal. "But they won’t start recognizing this until they see that they have less work," Kolawa continues. The key to success, he adds, is to have an infrastructure handle as much work as possible. "This way, developers have time to focus on the creative tasks they enjoy most...the ones that truly require human intelligence." View Dr Kolawa on SYS-CON.TV Read Dr Kolawa's Articles “Developers need to ... (more)

Emerging Trends and Software Quality Assurance

The future challenges for Software Quality assurance (SQA) follow a few software trends, including: Complex and large software packages Integration with external components and interfaces The need to deliver quickly The need to deliver bug free software The standard software quality activities defined by IEEE, such as verification and validation, are integrated into the software development cycle. We see dedicated SQA roles and resources in major organizations. Also, many multi-national companies are pushing to have a central team drive and manage the quality processes, methodolog... (more)

Jtest! by ParaSoft

ParaSoft's Jtest 3.0 is a powerful automated tool for testing Java classes. Developers can unit-test their code for completeness and standards compliance and conduct regression tests to ensure that changes they've made to their code haven't introduced errors. Environment I installed Jtest on an IBM Thinkpad 600E running Windows NT 4.0 Workstation, Service Pack 5, with 128MB of RAM. According to Jtest's documentation, it'll run on Windows NT/95/98, with support for Solaris and Linux coming in the next few releases. Minimally, Jtest recommends you run with a Pentium 233 with 128MB ... (more)

Product Review: Jtest 4.0

ParaSoft 2031 S. Myrtle Ave. Monrovia, CA 91016 888 305-0041 www.parasoft.com Test Environment: Toshiba Satellite Pro 4600, 866 MHz Intel Pentium III processor, 20GB disk, 256MB RAM, Windows 2000 w/Service Pack 2 Specifications: Platforms: Windows NT/2000/98/ME, Linux, Solaris Pricing: $3,495/developer New-car buyers often fear that they're getting a "Friday afternoon" vehicle - a car built by the last shift at the end of a tough week. Manufacturers have spent an untold number of man-years trying to prevent such defects. As developers you face the same problem: no matter how carefully ... (more)

Automated Error Prevention for Linux

Most organizations that use Linux as a business operating system are developing their own applications for Linux - perhaps in response to the current scarcity of packaged applications available on Linux. With so much internal development for Linux, it is critical that the IT groups building your Linux-based applications have a means to efficiently produce reliable code. If they don't, you will jeopardize the very reliability and cost-effectiveness that most organizations are trying to achieve by turning to Linux. However, most development teams follow a development process that ... (more)