Bartłomiej Hirsz
Bartłomiej Hirsz
According to style guide: https://docs.robotframework.org/docs/style_guide/guide#test-cases-or-tasks And https://docs.robotframework.org/docs/style_guide/guide#keyword
Add Robotidy Robot Framework library that works as a wrapper on our API and allows to call Robotidy in robot tests/tasks. From: https://robotframework.slack.com/archives/C01FR5992N6/p1700595648492519?thread_ts=1700595648.492519&cid=C01FR5992N6
Example  In this case NormalizeSeparator will still work.
Draft - used to run the test on different platforms.
For example: ``` FOR ${file} IN test_data/subdir/file.csv test_data/subdir/file2.csv test_data/subdir/file3.csv test_data/subdir/file4.csv test_data/subdir/file4.csv ``` to ``` FOR ${file} IN test_data/subdir/file.csv ... test_data/subdir/file2.csv ... test_data/subdir/file3.csv ... test_data/subdir/file4.csv ... test_data/subdir/file4.csv ``` or something similar.
Syntax for library import with aliased name was renamed. It could be separate transformer or one common transformer ReplaceDeprecated? Or allow to group transformers into "groups" for easier disabling/enabling.
For example RenameTestCases replace_to configured with " " will get "".
We're running our atest for every transformer separately (using --transform option). Whatever feasible we should run all default transformers with our tests. It should help with preventing issues like #507...
It's proposal of refactor for extracting keywords from result using Robot parsing API visitors. It should be tiny bit faster on larger files (150Mb+). I did not test it thorougly...