11 Matching Annotations
  1. Apr 2021
  2. Mar 2021
  3. Feb 2021
    1. You’re allowed to blame us for a terrible developer experience in Trailblazer 2.0. It’s been quite painful to find out which step caused an exception. However, don’t look back in anger! We’ve spent a lot of time on working out a beautiful way for both tracing and debugging Trailblazer activities in 2.1.
    1. Around 2 years ago I decided to end the experiment of “TRB PRO” as I felt I didn’t provide enough value to paying users. In the end, we had around 150 companies and individuals signed up, which was epic and a great funding source for more development.
  4. Jul 2020
  5. May 2020
    1. The test is being marked as skipped because it has randomly failed. How much confidence do we have in that test and feature in the first place.
    2. This policy allows the test suite to stay green while letting individual teams decide when they would like to put in the effort to write more deterministic tests. They may choose to do so right away, or delay until they work on the feature again.
    3. All tests that fail on the master branch will be considered flakes. These tests will be marked as skipped.