Building secure software makes business sense. Improved software security can improve revenue growth (as a competitive advantage), raise margins (through lower maintenance expense), improve customer satisfaction (fewer security patches and updates), and simplify regulatory compliance. As hackers increasingly target the application layer, organizations need to respond appropriately.
Software developers employ unit testing to individually scrutinize very small parts of an application (“units”), to test if they are operating properly. Unit tests are proven development testing activities for building quality into software, but only work as intended if they are written correctly, used consistently, and maintained as the code evolves.
An effective way to simulate dependent services that are out of your control for testing, service virtualization is a key enabler to any test automation project.
By creating stable and predictable test environments, your test automation will be reliable and accurate. But there are several different approaches and tools available on the market. What should you look for in a service virtualization solution to make sure that you’re maximizing your return on investment?
Use this guide to help you identify the key features and capabilities needed for your
successful enterprise deployment and adoption of service virtualization. It’s more important than ever to choose a solution that’s right for you and your organization.
The automotive functional safety standard, ISO 26262, provides some guidance on the software development and V&V processes, but it does not go in depth at the level of language constructs. To get such guidance, organizations turn to coding standards like MISRA C/C++ or AUTOSAR C++. In this paper, we explain how to comply with ISO 26262 by using a static analysis tool that’s configured with AUTOSAR C++ 14 compliance checkers.
This paper discusses what it really means to achieve coding standard compliance, using MISRA C 2012 and SEI CERT C as examples, and how to accelerate compliance with tool automation, dedicated reporting, and workflow management. The recommendations made here are generic and can b
This paper discusses what it really means to achieve coding standard compliance, using MISRA C 2012 and SEI CERT C as examples, and how to accelerate compliance with tool automation, dedicated reporting, and workflow management. The recommendations made here are generic and can be applied to any coding standard.
In this paper, we provide background information on ISO 26262 and its goals. We also discuss some of the policy-related issues associated with developing embedded software that complies with ISO 26262. Finally, we describe how Parasoft can help automotive software development organizations achieve compliance with ISO 26262.
Getting Started with Static Analysis
Static analysis is a powerful way to harden software, finding bugs and security vulnerabilities at the earliest stage of software development. But how do you start?
Read this guide to learn how to systematically introduce and integrate an advanced static analysis tool into your project, successfully.
Tired of waiting for test data?
Test Data Management (TDM) is a big problem for organizations, with the process of procuring, owning, and securing test data both a requirement and a liability.
Parasoft provides a modernized solution to solve these problems. Parasoft’s data simulation approach combines traditional test data extraction along with service virtualization, all in an easy-to-use web interface, so users can quickly build meaningful test data by capturing realistic test data from interactions between components in their existing system, and building data models that can be shared and controlled directly by testing teams. Download this white paper to learn more.