Cypress is a powerful and easy-to-use E2E testing framework that offers several advantages over other frameworks. Cypress also integrates with popular CI/CD tools, such as GitHub Actions, CircleCI, Buildkite, etc. This facilitates automating system testing workflows.
For our Testspace UI testing, we use the Jest test framework and Puppeteer for controlling the browser. One challenge we experienced when executing “headless” automated tests using our CI system was having no visibility of the active screen on a test failure. It soon became difficult to triage failures when we deployed more extensive testing scenarios.
Testspace has built-in integrations with GitHub Actions. To publish content simply “push” file(s) with the Testspace CLI. Test results, code coverage, and other artifacts can be published using a single command.
Testspace automatically discovers manual tests that are captured using “simple” plain text Markdown files and are committed to a repository. This approach follows the same process as software development - version control, pull requests for reviews, etc. The files are rendered as test instructions, allowing human testers to execute and provide status.
Learn how Testspace simplifies managing software quality and release readiness, by leveraging important information buried in your CI/Build systems.
A common practice for many development organizations, including ours, is to collect logs and data during automated testing. Whether this is done to provide context for failures or as secondary quality measurements, ancillary data can be a vital part of any Continuous Integration (CI) process. The challenge is how to collect and use the data efficiently and effectively, one that doesn’t include the manual triage and dissemination of data after each run.
We are introducing our second version of Test Analytics - Testspace Insights. This article provides an overview of the feature set and provides a brief description of other important metrics being considered for future releases.
Testspace supports integrations with two of the leading online Code Coverage providers; Codecov.io and Coveralls.io. Code coverage metrics are essential to effective Test Management and should be an integral part of any Continuous Integration (CI) system.
Here at Testspace we’re excited to introduce yet another Online VCS/CI Integration. Users of GitLab - a leader in Continuous Integration software - can now connect Testspace to their git repositories.
Testspace is used to measure and track metrics that help teams manage the quality of their software. Our goal is to provide actionable insights from test output produced during software development — Quality Analytics for the test automation workflow.
We are introducing the first version of Testspace Insights. This article provides an overview and sets the stage for future articles on the details of Insights and how to leverage them to improve the quality of the software development process.
The Testspace team is excited to announce a brand new integration with Bitbucket by Atlassian. Developers and teams using the popular Git hosting service can now connect Testspace to their git repositories.
Two standard workflows embraced by GitHub users are the Fork & Pull Workflow, with developers working on their personal copy of a repository (common for open source), and the Branching Workflow, with developers sharing repositories using multiple branches.
The benefits of deploying Continuous Integration (CI), as part of any Software Development process, have been well documented. One of the best articles, in our opinion, is by Joe Green from smrtr.co.uk, published on the Codeship Blog on 4-11-2013.
Our open source approach is based on following the lead of other companies in the industry. Thus we feel it’s important for Testspace to be free for open source development. To this end, we’ve integrated with GitHub and have ensured seamless operation with Travis CI.
A common reason why software companies struggle to maintain success is they’re unprepared for the inevitable growth in their software’s complexity and surface area. This inescapable increase in liabilities coincides with the thinning of budgets and headcounts as companies take on additional projects. Processes, sufficient during company and software infancy, collapse under the weight of the growing trend.