Skip to main content

Excel File Adaptor Example

Introduction

Through the Excel Adaptor, H-TEST can manage Excel files (of .xls and .xlsx types) and test them. It’s possible to perform single tests with this adaptor or end to end tests connecting with other adaptors either.

Initialization parameters

The Excel Adapter will attempt to read and parse the Excel sheet. The necessary initialisation parameters for this example are the following:

FilePath: Represents the full path and file name of the Excel file being handled by this instance of the Excel Adapter: C:\testURLsPERIODICOS.xlsx

Sheet: Indicates the sheet number of the Excel file we are going to work with: 1


Predefined functions (PF)

 

 

This is an example of interactionsa betweenUML Diagram which uses the GUI HTML Adaptor and Excel Adaptor Exercise

 

Statement of the exercise

With an Excel and a loop, open 6 web pages: Create an Excel with different URL's and collect them with TAST to open them in the GUI adapter.

Tip: use the function getNumColumns or getNumRows and use it as the end value of the loop. Use while or for loop of TAST

Solving the test case

In this first resolution, we have designed this test case using three Adapters: the User Object Adapter, the Excel FileAdapter, Adaptorand the HTML GUI Adapter. We have also created the WHILE loop, with otherwhich adaptorswe will execute the same steps, as long as the condition we indicate in anthe E2E test.

NECESITO IMAGEN

As partproperties of the mapping process, you should provide the Adaptor’s information, regarding to connect and use it:

  • FilePath: represents the full path and name of the Excel file that represents this instance of the Excel adapter.
  • NumSheet: indicates the number of the sheet within the Excel workbook on which we want to work.
  • Template: ifFragment is selected, the file will be created or overwritten in any case, with independence if the checkbox 'Create/Overwrite' has been selected.
  • Create/Overwrite: when the checkbox is marked, TAST will create a new file or overwrite it if the file already exists.
fulfilled.

 

Test Set Execution

After the test set execution, immediately you have the results. There are two main elements you can verify:

  • Logs: the step by step information of the execution, with:
    • the results.
    • the methods had been executed.
    • the timelines.
  • Evidences: the screenshots or evidence information by step, in case they have requested. Also the evidence file, in case they have requested as well.
Back to top