Understanding of a testing framework starts from the understanding of the task that a QA person faces. After determining that an application needs to be tested, the high-level task for the tester can be described as "to test". However, the simple verb - "to test" - does not explain what this means and doesn’t cover the amount of work that stands behind. Every QA engineer that needs "to test" an application has to find their own solution to the task. The testing framework that is created during this process is the basis of this solution.
So, a testing framework is a system that helps accomplish the task of application testing. I think that the minimal set of elements the simplest framework contains is as follows:
If we are talking about TestComplete, this is a TestComplete project with at least a single KDT or script test (#1). A tester runs the test on their PC (#2), and the log of the execution (#3) is saved to the project so the tester can analyze it. Of course, this simple scenario is not scalable enough and won’t be sufficient for many QA teams. So, let’s think about the way to improve every part of this simple framework.
Apparently, a single test is unable to confirm the quality of an application. Usually, there is a set of tests that a tester needs to manage. There are a lot of questions that could arise here:
Usually, a QA team needs to check whether their software works without problems in all possible environments (e.g., operating systems of different bitness, web browsers, mobile platforms) having different security permissions, user roles, paintings on a mousepad etc. When searching for a way to handle this stuff, a tester can consider a variety of options:
Managing different test environments is related to another problem that also needs to be solved: how to run tests in these environments. Here, in addition to custom solutions, there is a bunch of ready-to-use options, as well:
After getting results of a single test execution, a tester must decide what to do with them, and there are a lot of funny things that the QA person can do:
If you are interested in this topic, you may find more information on what a testing framework is and on how it can be built in the following webinars on the SmartBear website:
I described the above example not to tell you that this is the only and the right way to create a testing framework. This is just an example of what a testing framework could be. I would appreciate it if you shared your experience about how you built your testing framework and what difficulties you faced during this process. If you had some unusual tasks, it would be fascinating for everyone to learn about them and about the ways you accomplish them within your framework. Moreover, a testing framework can be something different from what I think it is, and this will make your story even more interesting for everyone.
Share your story and get a chance to get a gift from us:
PS: Your experience could be interesting for the TestComplete team, as well, and can have a chance to affect the future of the product.
Post your comments and give Kudos for comments you like. Tomorrow, we will announce a winner of Day 2 - a community member who will get the biggest number of Kudos for his/her post. Click here to learn the Day 1 winner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.