${TEST NAME} outputs a long strange string

Robot Framework
1

My test name is “testtest”，use “Log ${TEST NAME}”，i expect “testtest” but it outputs “7a398e4b5a2e4ce0b5851f3482b1c6d7testtest”.My RobotFramework version is 3.1.2

2

I doubt anyone can help you, even to reproduce your problem.

I recommend for you to setup a Python virtual environment, install Robot Framework 7.0.1, and then run the same test (possibly doing some fixes in test case). Probably, you will not see that problem.

1 Like
3

Hi @Dia-kiwi,

BTW which python version are you using? hopefully not jython? I’m not sure what python versions were supported with RobotFramework version is 3.1.2, but I wonder if you’re using a newer version of python that didn’t exist back then so that RF version has never been tested with that python version?

As @HelioGuilherme66 said I doubt anyone can help you with such an old unsupported version, it looks like the test name has been pre-pended with some form of GUID, probably some internal python reference ID, which is what makes me think you’re on a newer python version…

All I can suggest is either update to the current RF version or run RF 3.1.2 on an older python version i.e. python 3.6 if you can even still download those older versions?

Dave.

1 Like
4

Thank you for your reply. I think I understand the problem now. It seems that my RobotFramework version is indeed a bit outdated

1 Like
5

Thank you very much for your reply. Thanks to your inspiration, I went through the files of the engine project and found this information: Robot Framework 3.1.2 (Python 3.7.8 on win32). It seems that my Python version is also not suitable.

6

Hi @Dia-kiwi,

Python 3.7.8 is newer than what was around at the time of that RF version, but not so significantly newer, so while still possible I wouldn’t have expected that to be the issue, but I don’t know either, only testing that version of RF on several python versions will tell you. But it’s not worth spending too much time on it either as there won’t be any bug fixes to that old version of RF.

Do you need to remain on that RF version for some reason?

If not, I suggest create a branch of your test cases, run them on python 3.12.x with RF 7.0.1, and start updating your test cases to the newer RF version (many things have been deprecated since RF 3.1.2 and so there will be maintenance to do on your test cases), once you’ve updated all your test cases, merge the branch back to your main and update all your test machines to newest python and RF. The longer you stay on old versions the more issues you’ll have.

Dave.

2 Likes