Alignment of parameters in database related tool chain

[HolQue]

TestResultWebApp.pdf lists in section "Data Visualization" the following selection criteria: branch, variant, sw Version, component

RobotLog2DB.pdf lists in section "Robot Framework Testcase Settings" the following parameter: project, version_sw, version_hw, version_test, machine, tester, testtool

Finally the RobotFramework_TestsuitesManagement initializes the following parameter:

Set suite metadata 'project' to value 'RobotFramework Testsuites'.
Set suite metadata 'version_sw' to value ''.
Set suite metadata 'version_hw' to value ''.
Set suite metadata 'version_test' to value ''.
Set suite metadata 'machine' to value '...'.
Set suite metadata 'tester' to value '...'.
Set suite metadata 'testtool' to value 'Robot Framework 4.1.3 (Python 3.9.16 on win32)'.
Set suite metadata 'version' to value '0.6.0'.

(1) This partially does not fit together and should be aligned.

(2) In my opinion it makes no sense to let the RobotFramework_TestsuitesManagement initialize web application related parameters. For several reasons:

1. Already RobotLog2DB provides the possibility to define values missing in XML result files provided by Robot Framework.
2. A user that has Robot Framework together with RobotFramework_TestsuitesManagement installed, does not necessarily want to use the web application also. In this case the initialization of web application related parameters in every robot test is useless code.
3. Like I already mentioned in https://github.com/test-fullautomation/robotframework-testsuitesmanagement/issues/103 there is currently no possibility for a user to change the values of these parameters inside tests. Why do they need to be initialized with empty strings?

We have to clarify:

1. Which parameters do we want to have in the web application?
2. From where can we get the values (to be defined inside tests or imported from additional files)?
3. For all parameters that can be (or have to be) defined inside robot test files, we should pass the responsibility to the users. In my opinion the RobotFramework_TestsuitesManagement itself has nothing to do with this.

Just an idea: Maybe the RobotFramework_TestsuitesManagement can provide a separate keyword, something like initialize_reporting. And only the execution of this keyword during a test introduces a bunch of additional reporting parameters. But then it has to be explained already in the documentation of the RobotFramework_TestsuitesManagement, that this requires additional components (db app, web app) to be installed and belongs to a separate functionality.

[test-fullautomation]

Hi Ngoan, what is the status of this task? Thank you, Thomas

[ngoan1608]

Hi Thomas,

This ticket is related to the project/variant and other metadata information for the whole tool chain topic. For individual this import tool, the pull request https://github.com/test-fullautomation/robotframework-robotlog2db/pull/44 for updated document gives more information about them.

I suggest to close this ticket and track the metadata definition for whole tool chain in ticket https://github.com/test-fullautomation/robotframework-robotlog2db/issues/34.

Thank you, Ngoan