Closed srizzling closed 10 years ago
@robocoder I'm mentoring Sriram in this enhancement, and its very useful to our workflow. I guess first of all, we're looking for some feedback if this change fits in the vision for this extension, since it'll extend its scope quite a bit. I think provided good documentation, it can still form a coherent unit of operation. But if you think its better kept in a separate extension, we're happy to create one (reusing some of your existing code).
@robocoder I have implemented all of @chillu's recommendations. Could you possibly have a quick look and see if it fits your needs? From, what I can tell, I can try implement/cherry pick this https://github.com/vipsoft/JiraExtension/pull/11 because I can see it might not cleanly merge with this PR if you would like me to spend time on that.
Ok, will look at this today.
Hey @robocoder is there anything else you need from us on this?
I've merged this PR into the 2.5 branch. I'll merge into master (3.0.x-dev) later in the week.
Thanks :)
What it does?: This PR allows you to tag your scenarios with a specific Jira Ticket and after the test suite is completed, it pushes the resulting scenario text into specified Jira ticket ("feature_field").
Reason for new feature: This means that the feature files can be kept into source control, and still have a method for Buisness Users to read with direct access to the source code.
Problems Still to overcome: Not entirely sure how we will be able to hide the complications of branching to business users. With most development its key to make feature branches which last 1-2weeks, and it will be hard to keep track within this. If you have any suggestions I am open.
How to configure it: It installs as normal but it requires an extra config in the .yml file. Here is my sample .yml file: