Skip to content

CCK upgrade pathsΒ #1822

@luke-hill

Description

@luke-hill

πŸ€” What's the problem you've observed?

We're very far behind of CCK conformance

✨ Do you have a proposal for making it better?

Upgrade to CCK v22 in the v11 of cucumber-ruby. Then do the following upgrade paths

22->24

  • Likely to involve some breaking changes in namespacing of CCK proper
  • Will add in a few more samples - including a test run exception

24->26

  • Should be a fairly lightweight upgrade
  • Changes structure of some internals (So refactoring might be needed)

26->29

  • Internal structure changes again
  • Lots of new status style samples

πŸ“š Any additional context?

By the time these 3 upgrade paths have been done, we may have need for another set of upgrades

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions