Search results
Streamline ISO 26262 & ISO 21434 Compliance With Automated Testing
In the automotive industry, ISO 26262 addresses software safety in product development and outlines various testing methods to ensure the delivery of safe
vehicles. Similarly, many organizations must meet software security and verification requirements recommended by ISO 21434. Essential verification
methods like static analysis, unit testing, structural code coverage, and requirements traceability can be time-consuming and labor-intensive. Discover how …
Simplify Software Testing on Target Hardware
A notable challenge for embedded safety- and security-critical systems is optimizing target-based testing methodologies to validate the accuracy of
functionality, security measures, and performance parameters. Target systems exhibit distinct performance and behavior compared to their host
counterparts, which can significantly influence test outcomes, highlighting the need for tailored testing procedures. Static analysis raises code quality, whil…
How to Bypass the Microservices Testing Roadblock
Testing microservices can feel like an uphill battle—missing dependencies, scattered test results, and running full end-to-end tests after every small change. It
slows teams down. The architecture for microservices creates new challenges that piecemeal testing tools can’t keep up with. To make quality software at
scale, efficiently, you may want to try a comprehensive platform designed to make it less complex. Join us to learn how you can: • Eliminate bottlenecks …
What You Need to Know About Code Coverage for Embedded C/C++ Systems
Code coverage measures how much of an application’s source code is tested through various methods, such as unit testing, manual testing, and automated
functional testing. Code coverage percentage goals can be subjective. The thoroughness of the coverage in safety-critical systems depends on the
application safety integrity level (SIL) metric used in different industries and the development assurance level (DAL) commonly used in avionics. In building s…
Simplify Software Testing on Target Hardware
A notable challenge for embedded safety- and security-critical systems is optimizing target-based testing methodologies to validate the accuracy of
functionality, security measures, and performance parameters. Target systems exhibit distinct performance and behavior compared to their host
counterparts, which can significantly influence test outcomes, highlighting the need for tailored testing procedures. Static analysis raises code quality, whil…
Sysdig: What Code to Cloud Means For Your Business
As software development evolves, applications are becoming more reliant on the cloud. In fact, a recent survey revealed that 73% of organizations have
more than 50% of their applications deployed in the cloud. This makes protecting your applications from the first line of code to runtime and deployment in
the cloud more important than ever. Join Sysdig’s Director of Marketing Alliances, Eric Carter, and Checkmarx’ cloud security experts, Sagy Kratu and Mic…
Streamline ISO 26262 & ISO 21434 Compliance With Automated Testing
In the automotive industry, ISO 26262 addresses software safety in product development and outlines various testing methods to ensure the delivery of safe
vehicles. Similarly, many organizations must meet software security and verification requirements recommended by ISO 21434. Essential verification
methods like static analysis, unit testing, structural code coverage, and requirements traceability can be time-consuming and labor-intensive. Discover how …
On-The-Fly Java Unit Testing: Automate as You Code
Ensuring the reliability and stability of code is crucial, yet many teams still grapple with post-commit errors that disrupt workflows, cause build and regression
failures, and delay project timelines. A significant challenge is insufficient testing, where developers make code modifications without thoroughly validating
the changes. What if you could autonomously validate code changes, catch potential issues at the source, and help users create unit tests for their uncov…
STIM Customer Story: Making Sure your Code Withstands the Test of Time
In this webinar, Tobias Sjösten, Head of Software Engineering at Stim, tells the story of how they used Codacy to significantly improve and quantify code
quality across teams and projects, especially when dealing with legacy code. As a company that has existed for a century, Stim has a lot of legacy code, so it
was important to ensure that every new build could stand the test of time. Watch this webinar to dive deeper into their story, how they overcame some ch…
Close the Code Coverage Gap for Distributed Microservices
Code coverage is a unifying force between development and QA testers; however, it can be challenging to measure with microservices architectures. The
insights from code coverage visibility improve test strategies, increasing collaboration and mitigating the risk of untested code in production. End-to-end
testing is essential for verifying software functionality and compatibility, but it can also sometimes lead to compromises in regression test coverage as new …