robotframework / robotframework/robotframework-RFCP-syllabus
Reference to 'third' root suite option is missing; 'virtual suite' is made when RF is provided with multiple suite paths
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
In the current 'Root Suite' specifications we do not have a reference in the RFCP syllabus about what Robot Framework does when multiple paths are provided as a suite.
Example
robot my_tests.robot your_tests.robot
Source
This functionality is covered here in the user guide:
https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#specifying-test-data-to-be-executed
Quote from the User Guide:
The name of the created test suite is got from child suite names by concatenating them together with an ampersand (&) and spaces.
Decision
After discussing this in the syllabus comittee it was concluded we should refer to this functionality in the RFCE syllabus. To ensure this is remembered a github issue about this topic is raised, and will be labeled as RFCE relevant.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the RFCE syllabus's Root Suite specifications and the linked Robot Framework User Guide section on specifying test data. Add a reference covering multiple suite paths and the resulting virtual suite, including how its name is formed. Done means the syllabus reflects this agreed RFCE-relevant behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100