From the Pipeline v20.0

This entry is part 20 of 22 in the series From the Pipeline

The following will be a regular feature where we share articles, podcasts, and webinars of interest from the web.

Cucumber Reports

The creators of Cucumber have released a free, cloud-based service for sharing execution reports for scenarios. Both the Java and Ruby implementations of Cucumber have the report functionality built-in with simple commands or environment variables. If enabled, the console output links to an online execution report. The results will be available for a 24-hour period before being automatically deleted. In the future, the execution reports can be linked to a GitHub repo and will no longer be scheduled for auto-deletion if claimed.

Separating Automation Tooling from Automation Strategy

“When people do not have good luck with automation, it is hardly ever because of the tool being used, but almost always because of the wrong automation strategy, wrong expectations, and wrong adoption of automation. Automation tools only answer the “how” of automation, while having an automation strategy gives answers to who, where, when, what, and why. Here’s why it’s so important to have a test automation strategy.”

Ten More Commandments on Automation

Paul Grizzaffi provides an excellent overview of the common pitfalls organizations run into with test automation. His advice brings the same concepts we would expect from development code and applies is to test automation code because we should treat them the same way. Check to see if any of your test automation code breaks a commandment!

The Technical Debt Quadrant

The article a breakdown of the four types of technical debt as originally described by Martin Fowler. Sometimes we make deliberate mistakes either to simply push the product to production or because we don’t properly consider design. Other times our own inexperience with a technology means we make mistakes. How we react to that accrued technical debt determines if we are reckless or prudent about identifying the problem to help ensure we don’t repeat the mistakes again.

Webinar: Add Static Code Analysis to Your CI/CD Pipelines

Perforce recently hosted a webinar on static code analysis in CI/CD pipelines. Plenty of excellent lessons to learn about adding quality to deployment pipelines. “With the amount of software being installed into devices across all industries, it has become essential that the embedded code is safe and secure, reliable, and high quality. However, ensuring that the embedded code meets these standards and is delivered in a timely manner can be a daunting and time-consuming challenge. For that reason, it is essential that developers pair static code analysis with efficient software development practices, such as CI/CD pipelines. View this webinar and learn how to add static analysis to your DevOps process.”

Series Navigation<< From the Pipeline v19.0From the Pipeline v21.0 >>

Leave a Reply

%d bloggers like this: