Welcome to the Foresight Blog

Monitoring continuous integration pipelines allows developers to easily and securely understand/troubleshoot pipeline activity.

Change impact analysis can be done by an automated system that determines which lines are changed in a PR and are they tested or not with the existing test suites and tests

Traditional change management is often dismissed as slow, abstract, and limited in its usefulness. If we can automate the most important elements of change management into CI/CD, the benefits will be felt across the organization.

With all automation comes the requirement to see what’s happening. That’s why it’s crucial to monitor your CI/CD pipeline, just like you would monitor production applications.

We've implemented an open-source GitHub Action to generate and collect workflow telemetry data for CI pipelines. This Action monitors the resource metrics of the CI machine where the workflows run.

With test impact analysis, we have a solution to that problem. If we only run tests related to our changes, we can save time while still checking the crucial parts of our code.

Monitoring and debugging failed tests are one of the biggest challenges we face when maintaining our software. In this article, we look at what causes flaky tests & how to mitigate them.

In this article, we look at the challenges that test engineers face as their applications grow.

Selenium-4 has some significant improvement by shifting from Selenium-3