Parasoft
Parasoft's mission is to provide automated testing solutions and expertise that empower organizations to expedite delivery of safe and reliable software.
A powerful unified C and C++ test automation solution for static analysis, unit testing and structural code coverage, Parasoft C/C++test helps satisfy compliance with industry functional safety and security requirements for embedded software systems.
Learn more
TrustInSoft Analyzer
TrustInSoft commercializes a source code analyzer called TrustInSoft Analyzer, which analyzes C and C++ code and mathematically guarantees the absence of defects, immunity of software components to the most common security flaws, and compliance with a specification. The technology is recognized by U.S. federal agency the National Institute of Standards and Technology (NIST), and was the first in the world to meet NIST’s SATE V Ockham Criteria for high quality software.
The key differentiator for TrustInSoft Analyzer is its use of mathematical approaches called formal methods, which allow for an exhaustive analysis to find all the vulnerabilities or runtime errors and only raises true alarms.
Companies who use TrustInSoft Analyzer reduce their verification costs by 4, efforts in bug detection by 40, and obtain an irrefutable proof that their software is safe and secure.
The experts at TrustInSoft can also assist clients in training, support and additional services.
Learn more
PCOV
A standalone driver compatible with CodeCoverage for PHP is known as PCOV. When PCOV is not configured, it will search for directories named src, lib, or app in the current working directory sequentially; if none of these are located, it defaults to using the current directory, which can lead to inefficient use of resources by storing coverage data for the entire test suite. If the PCOV configuration includes test code, it is advisable to utilize the exclude command to optimize resource usage. To prevent the unnecessary allocation of additional memory arenas for traces and control flow graphs, PCOV should be adjusted based on the memory demands of the test suite. Furthermore, to avoid table reallocations, the PCOV setting should exceed the total number of files being tested, including all test files. It's important to note that interoperability with Xdebug is not achievable. Internally, PCOV overrides the executor function, which can disrupt any extension or SAPI that attempts to do the same. Notably, PCOV operates at zero cost, allowing code to execute at full speed, thus enhancing performance without additional overhead. This efficiency makes it a valuable tool for developers looking to maintain high performance while ensuring effective code coverage.
Learn more
PHPUnit
PHPUnit necessitates the activation of the dom and json extensions, which are typically enabled by default, alongside the pcre, reflection, and spl extensions that are also standard and cannot be disabled without modifying PHP's build system or source code. Additionally, to generate code coverage reports, the Xdebug extension (version 2.7.0 or newer) and the tokenizer extension must be present, while the ability to create XML reports relies on the xmlwriter extension. Writing unit tests is fundamentally a best practice for developers to detect and resolve bugs, refactor code, and provide documentation for a unit of software being tested. Ideally, unit tests should encompass all potential execution paths within a program to maximize effectiveness. Generally, a single unit test is aligned with one specific path in a particular function or method. Nonetheless, it is important to recognize that a test method may not function as a completely isolated or independent unit, as there can often be subtle dependencies between various test methods that stem from the underlying implementation of a test scenario. This interconnectedness can sometimes lead to challenges in maintaining test integrity and reliability.
Learn more
