![]() ![]() When something inevitably changes in Firefox that affects us, we want to know about it immediately so that we can respond. The Firefox code, which we are not responsible for, is 30 to 40 times the size of the code we are responsible for. Thunderbird is built from the Firefox code. Finding out when somebody upstream breaks us.This means a shorter feedback loop, and we can fix the problem before it annoys the users. If we test that some code behaves in an expected way, we’ll find out immediately if it no longer behaves that way. We’re not writing tests merely to make ourselves feel better. ![]() We want to find the bugs before our users do. Our code is going to be under more pressure than ever before – with a bigger team making more changes, and monthly releases reducing the time code spends on testing channels before being released. For a single change (or a group of changes that land at the same time), 60 to 80 hours of machine time is used running tests. For each change made to Thunderbird, our testing machines run a set of tests across Windows, macOS, and Linux to detect mistakes and unintended consequences. Automated testing increases the software quality by minimizing the number of bugs accidentally introduced by changes to the code. Since the release of Thunderbird 115, a big focus has been on improving the state of our automated testing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |