Uploaded image for project: 'Beaker'
  1. Beaker
  2. BKR-1527

Spike: Checkout Beaker DSL Inclusion Compatibility with Bolt Tasks



    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:

      Error rendering 'issue-templates-customfield'. Please contact your Jira administrators.

    • Epic Link:
    • Team:
      Quality Engineering
    • Story Points:
    • Sprint:
      QE 2018-10-03, QE 2018-10-17, QE 2018-10-31 🎃, QE 2018-11-14
    • QA Risk Assessment:
      Needs Assessment


      This task is to track a spike to see how much work it might take to transition away from beaker running tests to seeing if bolt can run beaker tests by including beaker DSL methods into tasks directly.

      I assume this isn't going to Just Work™, but the real question is how much work would it be to port Beaker's DSL methods so that they could be included in a bolt task? And are there any other gotchas we should be looking out for in moving tests to bolt tasks. So we're looking for a roadmap of the path to using bolt to run tests & estimates on how much work that looks like.

      At this point, the steps for this spike would be:

      1. get up-and-running with bolt & create some simple demo test tasks to use for later porting
      2. include the beaker DSL in the project, play around with some of the methods, see what breaks & how we can get through them
      3. port some actual tests from existing projects (puppet, pe_acceptance_tests) into bolt tasks, see how that looks different from the easy examples in 1 & 2

      I'm imagining at this point that it'll be about a sprint's worth of work for one person. I would imagine the more tests we can port in step 3, the more accurate of estimates we can get, it really just depends on the big unknown of how many different ways will things fail in step 2 & if we can get some spike solutions that let us continue as we loop through steps 2 & 3.




            kevin.imber Kevin Imber
            kevin.imber Kevin Imber
            0 Vote for this issue
            1 Start watching this issue



                Zendesk Support