Add the Functionality IDs in feature name & collection name
- Dominant language
- Java
- Stars
- 80
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
# Add the Functionality IDs in feature name & collection name
## Context
Currently, user can start with "Functionality 42: " prefix on both:
* Cucumber scenario name
* Postman request name
* Postman folder name
## Expected
In theory, a Cucumber .feature file is dedicated to only one feature/functionality.
Same would go for Postman collections.
So, allow users to add "Functionalities 42, 43: " prefixes in:
* Cucumber "Feature: " name
* Postman collection name
And functionality IDs in such places should be MERGED with functionality IDs in scenario names and in folders and request names (functionality IDs are ALREADY merged among Postman folders and request names).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing functionality-ID parsing and merge handling for Postman folder and request names, then trace the corresponding Cucumber scenario-name path. Extend the investigation to Cucumber Feature names and Postman collection names. Done means prefixes such as “Functionalities 42, 43:” are accepted and their IDs are merged with IDs from scenarios, folders, and requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postman
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100