Variables inside of classes in Variable Files are not recognized by the validations rules.

[daveesposito]

Example:

I have a variable file which contains the following:

class CATEGORY:
    ONE = "1"
    TWO = "2"

When I attempt to import this variable file into a test suite file it generates a warning "Could not find any variable in file '...'". Also, attempting to use the variables ${CATEGORY.ONE} or ${CATEGORY.TWO} (which is valid in Robot Framework) generates an error "Variable '...' is used but not defined".

Since this pattern is allowed by Robot Framework the variables should be recognized as valid.

[atiasn]

RobotFramework UserGuide Doc. resource-and-variable-files

Implementing variable file as Python or Java class

Starting from Robot Framework 2.7, it is possible to implement variables files as Python or Java classes.

Implementation

Because variable files are always imported using a file system path, creating them as classes has some restrictions:

• Python classes must have the same name as the module they are located.
• Java classes must live in the default package.
• Paths to Java classes must end with either .java or .class. The class file must exists in both cases.

[michalanglart]

Hi,

this requires some investigation on our side. As @XiaoyaoRay pointed out the User Guide states that the class should have same name as the module.

In your example if you rename your module to CATEGORY you will properly be able to use ONE as well as TWO variables and RED will not complain.

This is true however that Robot allows to use ${CATEGORY.ONE} syntax and runs happily despite of what is stated in user guide.

We need to take a look at this deeper.

[daveesposito]

Yes, my observation is that I can have multiple classes in a variable file and when I run the tests Robot Framework will correctly identify all variables. Also, they are recognized in RIDE as well.

[michalanglart]

Closing - released in 0.8.8