Overview One of the most challenging things about coding is when your code doesn’t work and you have to figure out why. Trying to track down a problem can be half the battle. You might not know what’s causing the problem, how to fix it, or where to look in the first place. This can
We’re pleased to say that we’ve qualified pjproject 2.9 with Asterisk and that the recent 13.28 and 16.5 Asterisk releases have the bundled pjproject updated to the new version. All of the patches against pjproject 2.8 we’ve previously submitted upstream to Teluu (the maintainers of pjproject) were accepted but since the release of 2.9, we’ve
Back in December in my The Continuing Saga of Continuous Integration blog post I wrote about how we reduced the Testsuite’s “27” layers of file system access down to 3 by moving the Docker container’s /tmp filesystem to be memory backed. That reduced the number of individual test failures by quite a bit but still
or… “Watch This Space” If you’re an Asterisk contributor you’ve probably noticed that we’d been having issues with large numbers of Jenkins test failures during the “gate” phase of the Gerrit review process. Some tests were failing consistently and others seemed random. After a lot of head scratching we finally figured out the major contributor
Measuring performance in Asterisk, like most software systems for that matter, can be a complicated task. When testing performance it is important to define goals, and limit the context for that which is being tested. It’s been previously shown that res_pjsip might have an efficiency problem when it comes to inbound registration. Our main goal for this
Let’s talk some more about testing, understanding the test framework for Asterisk, and building better tests. An exciting topic I know! In a previous post, we discussed how unit testing Asterisk worked. Here, though we’ll be talking a bit about the Asterisk Test Suite. The Asterisk Test Suite is a way to write automated, functional, “black-box”
How much testing do we really do? A lot, and let’s face it, Asterisk isn’t the easiest of software packages to test. Our continuous integration environment could run over 1000 tests on a single change before it’s merged into the codebase. Unfortunately, without a significant amount of work, mostly around directory and port coordination,
Continuous integration isn’t something that many people in the Asterisk project think about but it is a critical part of the development of Asterisk. It provides assurances on changes that go in and allows us to find problems faster, usually before a release occurs. The first introduction someone may have to our continuous integration is
