|
|
| Line 1: |
Line 1: |
| = Rubygem Cucumber 7.1.0 =
| |
|
| |
|
| == Summary ==
| |
| Rubygem-cucumber 7.1.0 is the latest version of the popular integration BDD test suite for Ruby.
| |
|
| |
| == Owner ==
| |
| * Name: [[User:Jackorp1 | Jaroslav Prokop]], [[User:pvalena| Pavel Valena]]
| |
| * Email: jprokop@redhat.com, pvalena@redhat.com
| |
|
| |
| == Current status ==
| |
| [[Category:ChangePageIncomplete]]
| |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
|
| |
| [[Category:SelfContainedChange]]
| |
|
| |
| * Targeted release: [[Releases/36 | Fedora Linux 36 ]]
| |
| * Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
| |
| <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
| |
| Bugzilla state meanings:
| |
| ASSIGNED -> accepted by FESCo with ongoing development
| |
| MODIFIED -> change is substantially done and testable
| |
| ON_QA -> change is fully code complete
| |
| -->
| |
| * FESCo issue: <will be assigned by the Wrangler>
| |
| * Tracker bug: <will be assigned by the Wrangler>
| |
| * Release notes tracker: <will be assigned by the Wrangler>
| |
|
| |
| == Detailed Description ==
| |
| Fedora is currently lagging behind on the Ruby cucumber test suite and as a result on new features and bug fixes. Therefore the rubygem-cucumber library stack will be updated to version 7.1.0, ensuring that Fedora has the newest Ruby cucumber test suite available.
| |
|
| |
| == Benefit to Fedora ==
| |
| This update will bring Rule and Rule tags, new hooks, and better plugin support into Fedora as well as other improvements like bug fixes and features in the dependencies that are part of the Cucumber project.
| |
|
| |
| == Scope ==
| |
| * Proposal owners:
| |
| * rubygem-cucumber and its dependencies will be updated.
| |
| * Build rubygem-cucumber update and dependencies in sidetag.
| |
| * Rebuild packages that depend on rubygem-cucumber and fix any that begin to fail as a result. <!-- not sure if there will be any failures, TODO: maybe delete? -->
| |
|
| |
| * Other developers: TODO <!-- not sure what would they be doing... fixing failures? AFAICT it is pretty backwards-compatible regarding Gherkin specs... -->
| |
| * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue.
| |
| The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
| |
|
| |
| * Trademark approval: N/A (not needed for this Change)
| |
| <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
| |
|
| |
| * Alignment with Objectives:
| |
| <!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
| |
|
| |
| == Upgrade/compatibility impact ==
| |
| Upon upgrade it should still work for all users.
| |
| The only exception being the HTML output formatter which is currently not planned on being packaged.
| |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| |
| == How To Test ==
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
|
| |
| Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
| |
|
| |
| A good "how to test" should answer these four questions:
| |
|
| |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this change? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the change is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| -->
| |
| Tests that are running under rubygem-cucumber 3 are expected to run under rubygem-cucumber 7 as well.
| |
|
| |
| 1. Prepare:
| |
| To test using DNF, simply run
| |
| dnf install rubygem-cucumber
| |
|
| |
| 2. Running the tests
| |
| Find a project that uses rubygem-cucumber 7.1.0 test implementation, and in that project run:
| |
| $ cucumber
| |
|
| |
| 3. Checking the results
| |
| All tests should proceed as they do upstream without crashing.
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| |
| == User Experience ==
| |
| * New rubygem-cucumber version 7.1.0 available
| |
|
| |
| == Dependencies ==
| |
| * There are several packages, which depend on the rubygem-cucumber test suite as their Build requirement.
| |
| * These need to be updated: (none)
| |
| * Following gems don't support rubygem-cucumber 7.1.0 right now and would be broken by the update: (none)
| |
|
| |
| == Contingency Plan ==
| |
|
| |
| * Contingency Plan
| |
| * Contingency mechanism: None needed. rubygem-cucumber with its dependencies will be built in a side-tag and merged after successful updates.
| |
| * Contingency deadline: N/A (not a System Wide Change)
| |
| * Blocks release? No
| |
| * Blocks product? No
| |
|
| |
|
| |
| == Documentation ==
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| N/A (not a System Wide Change)
| |
|
| |
| == Release Notes ==
| |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.
| |
|
| |
| Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
| |
| -->
| |
| Users can use 'dnf install rubygem-cucumber' to install rubygem-cucumber.
| |
