robotframework / robotframework/robotframework-RFCP-syllabus
Integration testing could be better Component integration testing
Open
Nobody has claimed this yet.
state: needs-triage
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Integration testing could better be called ‘component integration testing’, because just before the statement is made that RF is very suitable to be used for System integration testing
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
Open website/docs/chapter-01/01_purpose.md at the linked section around line 44 and read the surrounding distinction between integration testing and system integration testing. Update the terminology to clarify component integration testing, then verify that the paragraph remains consistent with the surrounding text.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100