Conversational idea of RIT

Owned by Eliot Muir
Last updated: Nov 11, 2023
1 min read

Stability and making sure that problems when encountered and solved and stay solved are a huge part of our focus right now.

We’re been methodically asking the question with each problem we resolve:

  • RISK

  • IMPACT

  • TEST STRATEGY

RISK

What is the risk of something breaking again. How likely are we to encounter that problem again?

IMPACT

What is the impact of this problem if it were to happen again. This gives us a good tool to think about how much effort should be spent on testing and automating the testing of this issue.

TEST STRATEGY

What is the strategy for testing the problem to detect if it comes back. When possible we try to find automated ways to test things since these are the easiest for us to scale up as our test coverage gets higher and higher.

We have an excellent Build system which runs immediately on every git push. As part of the development of IguanaX I designed a new multi-threaded C++ unit testing framework which runs the tests on multiple threads. That lets us run more tests, faster.

Â