Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-6730

SPIKE Standardize Windows Modules: Determine the standard set of platforms CI tests against

          Details

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

            The output from this ticket should be a documentation of our agreed-upon standardization of default platforms our modules run against.

            NOTE: in order to implement this, the module using this default should implement testmode switcher in order to use the same tests for smoke acceptance step as well as the full acceptance step.

            Scrape CI-job config for windows test matrices and compare with group.

            • Document changes to the default platform set in the CI Job Config YAML files so that future-you knows why it is different.
            Show
            The output from this ticket should be a documentation of our agreed-upon standardization of default platforms our modules run against. NOTE: in order to implement this, the module using this default should implement testmode switcher in order to use the same tests for smoke acceptance step as well as the full acceptance step. Scrape CI-job config for windows test matrices and compare with group. Document changes to the default platform set in the CI Job Config YAML files so that future-you knows why it is different.
          • Epic Link:
          • Team:
            Windows
          • Sprint:
            Windows Kanban
          • QA Risk Assessment:
            Needs Assessment

            Description

            In Jenkins there are many different platform matrices we tests individual modules against. They should be as standard as is sensible.

            We (Glenn and I) believe that it makes sense, as a default, for modules to run Smoke Acceptance tests in a master/agent redhat/2012r2 configuration running only the high priority marked tiers of acceptance tests. This will give us coverage against master/agent conflicts of the type:

            • 256 character path limit
            • module incompatible with linux masters (additional investigation for travis-only testing at MODULES-6553)

            Further the proposed full PE acceptance tests matrix, by default, should be something like (i.e. this is open to modification and we require input/buy-in from the team) in agent-only configuration:

            • 2008r2
            • 2012
            • 2012r2
            • 2016core
            • 2016

            This work involves:

            • testmode switcher
            • test tiering
            • rspec (for QAELK reporting)

              Attachments

                Issue Links

                is blocked by

                Task - A task that needs to be done. MODULES-6731 SPIKE Standardize Windows Modules: convert all windows modules to beaker rspec

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Resolved

                Task - A task that needs to be done. MODULES-6733 SPIKE Standardize Windows Modules: ticket the addition of testmode switcher for all Windows modules

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Resolved
                relates to

                Improvement - An improvement or enhancement to an existing feature or task. MODULES-6553 Standardize Windows Modules CI and Test Execution: SPIKE use Travis CI to test windows modules on linux

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Accepted

                  Activity

                    People

                    • Assignee:
                      erick Erick Banks
                      Reporter:
                      erick Erick Banks
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support