allow input filenames in the same format as Robot

KrzysztofJozefowicz commented 7 years ago

Hi currently RfLint accepts either path to filename or folder with recursive search. It would be very useful to allow user to use Robot format for TestSuites as well so the same arguments for Robot could be used in RfLint: What I mean is to:

allow use of --suite/-s switch together with project path: http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#by-test-suite-and-test-case-names together with project path
allow to use -t to specify which test from suite to check

boakley commented 7 years ago

I will consider this, but I doubt that I will implement it. I don't see any value to adding this feature.

The main purpose of the tool is to check whole files, not individual tests. Why do you need to specify specific files, and why can't you specify suites by simply providing that suite as an argument?

KrzysztofJozefowicz commented 7 years ago

Hi This is connected with #44, if user already can create argument file for robot testrun, it would be consistent to use the same argument file as input for rflint. One way of specifying suites is to provide a path to project and path to suite by -s ProjectName.SubFolders.SuteName path-to-project This is the case where testSuite is not defined by system path with extension.

boakley commented 7 years ago

I don't understand this statement: "This is the case where testSuite is not defined by system path with extension."

All robot test suites by definition must have a path on the system. The definition of a robot suite is a file or a directory.

On Tue, Jun 13, 2017 at 7:26 AM, Krzysztof Jozefowicz < notifications@github.com> wrote:

Hi This is connected with #44 https://github.com/boakley/robotframework-lint/issues/44, if user already can create argument file for robot testrun, it would be consistent to use the same argument file as input for rflint. One way of specifying suites is to provide a path to project and path to suite by -s ProjectName.SubFolders.SuteName path-to-project This is the case where testSuite is not defined by system path with extension.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/boakley/robotframework-lint/issues/43#issuecomment-308099420, or mute the thread https://github.com/notifications/unsubscribe-auth/ABEmYlbn--k63Bz_Ws-_o8iojwREJSClks5sDn_YgaJpZM4N4Osq .

KrzysztofJozefowicz commented 7 years ago

Let me provide example what I meant by " testSuite is not defined by system path with extension." Consider following folder tree:

/home/myRobot -- mytest.robot -- subdir/mytest2.robot

Robot & RfLint can execute following suites by robot eh: robot /home/myRobot/mytest.robot or robot /home/myRobot/subdir/mytest2.robot there is also -s switch which can run suites as follows : robot -s myRobot.mytest /home/myRobot or robot -s myRobot.subdir.mytest2 /home/myRobot

This way only project/parent dir path is specified, suites follows path by dir.subdir.suite

boakley / robotframework-lint

allow input filenames in the same format as Robot #43