Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-2051

Refactore the "create" method in the test automation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 0

      Currently, when we create a new resource in the test automation we do it by calling the "create" method in the resources.

      It is like that because that was the first approach followed by the first automated test cases. A cleaner solution would be to use a Create function for every resource, being every resource located in its own package.

      We can refactor the code so that:
      1- Every resource is located in its own package
      2- In every resource package we have a function to Create, to Delete and to instance resources with New.

              Unassigned Unassigned
              sregidor@redhat.com Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: