Skip to content

Instantly share code, notes, and snippets.

@omaciel
Created May 17, 2016 13:00
Show Gist options
  • Save omaciel/b4b5bdd73ea3eecc631b065236e3bb5a to your computer and use it in GitHub Desktop.
Save omaciel/b4b5bdd73ea3eecc631b065236e3bb5a to your computer and use it in GitHub Desktop.
Polarion + Betelgeuse + Testimony

Polarion Tooling Meeting

Question

Can you present an example test case that you would want to import, including:

  • Source of the test
  • Title
  • Description
  • Metadata - Required Fields
    • Component
    • Pos/Neg
    • Importance
  • Metadata - Not Required Fields (If available)
    • Setup
    • Teardown
    • Test Steps
  • Likelihood of changes - example if possible

Answer

All attributes and metadata for a given test case will be present in the source code for automated test cases:

def test_positive_create_with_non_default_lce(self):
    """@title: Create Activation key with associated custom environment
    @Requirement: Activation key
    @Level: Acceptance
    @Component: CLI
    @Type: Functional
    @Importance: Medium
    @Upstream: No
    @Setup: Create a new user with 'admin' role. Use this new user to
        create a new organization and custom lifecycle environment.
    @Steps:
        1 - Create a new activation key associated with the newly
        created lifecycle environment
    @Assert: Activation key is created and associated to expected
    lifecycle environment
    """
    env = make_lifecycle_environment({u'organization-id': self.org['id']})
    new_ak_env = self._make_activation_key({
        u'lifecycle-environment-id': env['id'],
    })
    self.assertEqual(new_ak_env['lifecycle-environment'], env['name'])

Links

  • Testimony should consider reading properties at the module and class levels in addition to method level - SatelliteQE/testimony#93
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment