Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15261

Verify we have Elytron variants of important web tests

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • Security, Test Suite
    • None

      Overall we should probably ensure we have a reasonable smoke test under smoke to ensure it is executed for all local builds. We should double check the expected layers to work with smoke but we should have something using a number of subsystems and smoke testing a propagation example.

      • Undertow
      • EJB
      • WS
      • Rest
      • JCA
        i.e. the smoke test catches an obvious breakage in local builds before a PR is submitted.

      All web / security testing should then move to either web or elytron. The elytron testsuite should likely be reduced down to items that are specifically testing Elytron e.g. ACME testing, general security a web application should likely be under web.

      A lot of web testing also seems to be under basic, as we have a dedicated area for web we should likely clean those up as well.

            Unassigned Unassigned
            darran.lofthouse@redhat.com Darran Lofthouse
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: