Overview
Readysell's , as all software, has as few some bugs in it as is reasonably possible. Readysell manages bugs by following . We try to keep the number of bugs as low as reasonably possible by adhering to a number of defined practices, however we are always balancing quality with how quickly and efficiently we can delivery new functionality and this can lead to the occasional bug in the software.
These tried and tested software development procedures that have been proven and accepted by many software developers over time:
See https://en.wikipedia.org/wiki/Software_bug
Procedure
Readysell's software quality control procedure is as follows:practices are used by many software developers facing similar challenges. We believe we have the right mix of speed and efficiency of delivery and stability, but are always happy to hear your feedback.
Issue Tracking
All customer-reported issues are tracked in our support system (see Readysell Support Policy for more details). If the issue is deemed to be caused by a bug in the Readysell software, that bug is logged in our internal bug-tracking system. This allows us to record all the required details about the bug and track it through development, testing and deployment.
Automated Testing
Readysell has some automated testing of key components to ensure that issues introduced by programming errors are picked up as early as possible in the process. We continue to invest in expanding our automated testing to improve test coverage.
Internal Testing
Once our developers have addressed a bug, the bug is handed over to our internal testers for testing. Our testers will follow pre-defined reproduction steps to determine the issue has been resolved. They will also perform exploratory regression testing to ensure that no new issues have been introduced as a result of fixing the addressed bug. The tester will go back to the developer if any issues are found with the bug fix, and once they are satisfied, will mark the bug as "Testing Passed" in our internal bug-trackign system.
Piloting
Once internal testing of the addressed bugs in a new version is completed, that version is deployed to a small set of volunteer customers who provide direct feedback and telemetry to ensure that the update does not cause new issues in a production environment.
Staged Rollout
After a short period of piloting (typically 1 or 2 days), we commence staged rollout of the new version to customers. Customers are placed into deployment "rings" that dictate this rollout. If you would like to know which ring you are part of and/or change rings, please contact Readysell support.
| Ring Name | Number of Customers | Description |
|---|---|---|
| Fast Ring | ~10% | First group of customers after the pilot to receive an update. Typically customers with whom we have a particularly close working relationship and can provide timely and quality feedback. |
| Slow Ring | ~20% | Next group of customers to receive and update. Typically a mix of customers with different operational practices and configurations to ensure that an update works correctly in various conditions. |
| Stable Ring | Remainder | Final rollout of a Readysell update to entire customer base. |
See also
- Software bug at Wikipedia