As the gold standard for web-based building design software, testing and improving SmartBuild Systems for our users is always a top priority.
While some of our testing is manual due to the 3D modeling nature of SBS, we also rely heavily on automation and regression testing.
Both processes are essential for detecting and fixing bugs and creating the best user experience possible.
Automation testing is useful for checking specific actions that can be repeated multiple times.
Things like outputs, setup wizard, adding, deleting, changing materials, and saving are good candidates for automation testing.
When running automation tests for SBS, we use coded programs that perform these actions and functions and then review the results.
Automation testing allows us to uncover bugs that might have gone unnoticed during in-person tests. Then, we implement plans to repair them for an improved user experience.
Regression testing is the process of re-testing a website after changes have been made to ensure that the new developments haven’t introduced new bugs or broken existing functionality.
Running a regression test is often a more involved and lengthy process than automation testing, but it’s also more thorough and can uncover deeper functionality issues.
As SmartBuild Systems evolves, new features are added regularly, requiring frequent regression testing.
The process looks something like this:
- Identify SmartBuild’s key features and functionality, such as forms, buttons, links, and data displays.
- Then create test scenarios for each feature and functionality, such as testing the edit view, job review, drawings, outputs, button clicks, and data display.
- Create a set of specific test steps and expected results for each testing scenario.
- Test the web page using these test scenarios and document any bugs or issues found.
- Repeat the testing process multiple times to ensure all features and functionality are operating correctly.
Another testing process we routinely go through is Beta Testing. After we have gone through all the testing processing outlined above in this blog, we post the new release to our Beta Test site, usually for a week before our final release. During this period, we invite any customers who want to get an early look at new features to log into the beta site, try the new software, and report their observations, including suspected bugs, so our team can fix and fine-tune them before the final release.
If you want to participate in the Beta Test process, just let us know, and we’ll put you on the list.
How You Can Help Out
While we strive for bug-free releases, the number of ways SmartBuild Systems can be used is nearly as numerous as our customers. It’s possible you may run across bugs and functionality problems that don’t turn up in our tests.
If that happens, please report them to the support team, and we’ll address them as quickly as possible.
In order to provide you and your customers with an optimal user experience, we want to do everything we can to ensure that SmartBuild Systems is functioning correctly and meeting your every need.