Trunk

Trunk now supports SSOs for teams on the enterprise plan. If you're interested in configuring SSO for your team, contact us. Learn more about SSO: https://lnkd.in/gwzA6qpV

Trunk now supports SSOs for teams on the enterprise plan. If you're interested in configuring SSO for your team, contact us. Learn more about SSO: https://lnkd.in/gwzA6qpV

🤔 Can you reliably catch flaky tests before they’re merged into your repo? Yes, but no. You can catch most flaky tests by re-running your entire test suite many times before merging. Even then, you still might miss some flakes. To detect tests with a 1% flake rate with 95% confidence, you’d need to run it about 300 times! [1] Studies have also shown that even with 500 runs, you’re likely to miss many flaky tests (up to 75%, depending on the project), and initial attempts to fix flaky tests fail to eliminate flakiness. [2] You need to combine active prevention and continuous monitoring to eliminate flaky tests in your repo. Stop hitting rerun and try Trunk Flaky Tests: [link from Buffer] References: [1] https://lnkd.in/gj3fzK-t [2] https://lnkd.in/gh7NBDPQ

🤔 Can you reliably catch flaky tests before they’re merged into your repo? Yes, but no. You can catch most flaky tests by re-running your entire test suite many times before merging. Even then, you still might miss some flakes. To detect tests with a 1% flake rate with 95% confidence, you’d need to run it about 300 times! [1] Studies have also shown that even with 500 runs, you’re likely to miss many flaky tests (up to 75%, depending on the project), and initial attempts to fix flaky tests fail to eliminate flakiness. [2] You need to combine active prevention and continuous monitoring to eliminate flaky tests in your repo. Stop hitting rerun and try Trunk Flaky Tests: [link from Buffer] References: [1] https://lnkd.in/gj3fzK-t [2] https://lnkd.in/gh7NBDPQ

🤔 Can you reliably catch flaky tests before they’re merged into your repo? Yes, but no. You can catch most flaky tests by re-running your entire test suite many times before merging. Even then, you still might miss some flakes. To detect tests with a 1% flake rate with 95% confidence, you’d need to run it about 300 times! [1] Studies have also shown that even with 500 runs, you’re likely to miss many flaky tests (up to 75%, depending on the project), and initial attempts to fix flaky tests fail to eliminate flakiness. [2] You need to combine active prevention and continuous monitoring to eliminate flaky tests in your repo. Stop hitting rerun and try Trunk Flaky Tests: [link from Buffer] References: [1] https://lnkd.in/gj3fzK-t [2] https://lnkd.in/gh7NBDPQ

We're excited to announce our new Senior Software Engineer at Trunk, Ben! In his own words, "Flakiness is for pastries—not tests! A craftsperson is not their tools—but good tools make a big difference! I’m excited to join the great team at Trunk, to work on improving devs’ lives and helping companies to ship better. At home in the Pacific Northwest I’m surrounded by dogs, cats, books, and board games, and make sounds on synths.”

Our Jira integration now tracks ticket assignments and status changes in your flaky test timeline. See the complete story of your flaky tests—from detection to assignment to resolution—all in one place. See full change log: https://lnkd.in/gwfWwnak

🤔 Developers, what percentage of your testing time is spent on unit tests vs integration tests? And what type of code base do you work on? Comment below

Hand-holding a PR through testing to merge can be challenging in a busy repo. You might face: - Constant need for manual rebasing - Time-consuming logical merge conflicts - Difficulty maintaining a stable main branch - Delays in the development pipeline due to merge-related issues Learn how Cavnue ships hundreds of PRs a month and 89,000 lines of code changes without compromising on speed or quality:

Our Jira integration now tracks ticket assignments and status changes in your flaky test timeline. See the complete story of your flaky tests—from detection to assignment to resolution—all in one place. See full change log: https://lnkd.in/gwfWwnak