Forum Discussion

HirendraSingh's avatar
HirendraSingh
Contributor
4 hours ago

TestComplete recording feature.

Has anyone using TestComplete recording feature for developing Data Driven testing and Is it fast as compared to using darg and drop approach in TestComplete itself?
Which is more effective or fast and reliable, can anyone give some genuine examples which I can explain to my management.

3 Replies

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3

    Data-Driven Testing is a software testing methodology where test scripts are designed to read input data and expected outcomes from external data sources. This approach separates test logic from test data, allowing the same test scripts to be executed with multiple sets of input data. It's a technique for improving test efficiency and coverage. Its benefits in terms of flexibility, reusability, and scalability.

    If you don’t use Data-Driven Testing, the main difference is that test data is hard-coded directly inside the test scripts instead of being stored externally. This changes how tests are written, maintained, and scaled.

    For example, if you have 50 different input data sets to test in a calculator application, the best approach is to use Data-Driven Testing. Instead of writing 50 separate test cases, you write one test script and execute it 50 times using different data inputs.

    • HirendraSingh's avatar
      HirendraSingh
      Contributor

      I want to know that is TestComplete's recording feature can be used to create tests effectively, In which multiple If then, loops conditions are used. Which is more flexible to use recording or drag and drop approach while creating keyword tests.

      • rraghvani's avatar
        rraghvani
        Icon for Champion Level 3 rankChampion Level 3

        If you look at the video shown in Preparing Data for Data-Driven Testing, you can see how easy it is, setting up DDT, with a few simple steps. You define your test once, and pass in your data 50 times. Whereas, using keyword actions ("drag and drop") to define 50 tests is time consuming.

        Regardless whether you are scripting or using keyword test, the same principle applies. If you want to reduce or increase your data, it can be easily done with DDT. Whereas, keyword actions, you'll need to remove or add keyword actions, which is time consuming.

        See Data-Driven Testing, there's plenty of examples.