Like all software, Noibu is subject to sporadic and unpredictable down time due to global updates or unexpected issues. We have designed the NoibuJS script with this in mind. We know that site performance and speed is crucial to all eCommerce stores and have built an architecture to isolate our back-end functionality from our script.
Noibu stores and analyzes information about errors on separate servers, which means that the script is only tasked with sending information back to those servers. If our backend services were to shutdown, the Noibu script would not be aware of those failures, and the outage would not impact your customers.
We also have a separate logging infrastructure for errors thrown by our script. If the NoibuJS script is malfunctioning and causing your site to behave unexpectedly, our system alerts us almost instantly that something is amiss. However, to avoid the script malfunctioning, we have rigorous manual and automated testing in place to catch script issues before they cause significant strain. These testing protocols include:
- Unit testing to check that our code works as expected.
- End-to-end tests to test how our script interacts with a real website.
- Integration tests to ensure our script functions as expected with backend components.
- Manual QA testing on real customer websites. In these tests, we load our script as an extension so it only impacts the QA tester.