Article Preview
Buy Now
COLUMN
Software Testing
Xojo thoughts, news, and tips
Issue: 23.6 (November/December 2025)
Author: Paul Lefebvre
Author Bio: Paul Lefebvre is a Xojo Software Engineer. He has been using Xojo and its prior versions since 2001.
Article Description: No description available.
Article Length (in bytes): 10,606
Starting Page Number: 42
Article Number: 23607
Related Link(s): None
Excerpt of article text...
Contrary to what many people who aren't developers think, being a developer is not only about writing code. There is much, much more to it, and one of those other things I'd like to talk about today is testing.
Testing is the process of verifying that your software works the way you expect, and it is a common issue that users complain about. When software doesn't work as expected, users will say it is buggy. It doesn't matter what the software is—be it Xojo itself, macOS, Windows, or some other app—users will always find and complain about bugs, so it's always best to try and find as many as you can before they do.
How do you test and find bugs in the software you create?
There are several levels of testing, and the first one that you can do is simply run the project. You write some code, run it, and then use it to see if it works. But how do you know that it is working? The key thing to focus on is, "Do the results match expectations?"
When you write code, you expect it to do something. When you test the code, you are essentially verifying that it works as expected. However, doing that testing manually by clicking around in your app is tedious, and you are likely to miss something.
What if there were a way to automate this somehow?
...End of Excerpt. Please purchase the magazine to read the full article.