Details

    • Type: Task Task
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2
    • Fix Version/s: 2.3
    • Component/s: Libraries
    • Labels:

      Gliffy Diagrams

        Issue Links

          Activity

          Hide
          Petr Skoda added a comment -

          I think this should be integrated soon so that we have enough time to find all problems and resolve them

          Show
          Petr Skoda added a comment - I think this should be integrated soon so that we have enough time to find all problems and resolve them
          Hide
          Eloy Lafuente (stronk7) added a comment -

          Integrated, thanks!

          Surely it would be interesting to have one detailed list of YUI artifacts to be tested in core, so each time we update the library, everything can be checked.

          Show
          Eloy Lafuente (stronk7) added a comment - Integrated, thanks! Surely it would be interesting to have one detailed list of YUI artifacts to be tested in core, so each time we update the library, everything can be checked.
          Hide
          Tim Barker added a comment - - edited

          Ran the current Selenium tests against this to check for regressions. Coverage includes multiple yui elements. All tests passed!

          Show
          Tim Barker added a comment - - edited Ran the current Selenium tests against this to check for regressions. Coverage includes multiple yui elements. All tests passed!
          Hide
          Tim Barker added a comment -

          This type of testing is very suited to the Selenium test automation suite.

          I agree with Eloy, to plan a good suite of regression tests I will need a list of UI elements. Without this I cannot build a coverage map or plan yui targeted regression testing properly. If we did this, the regression testing of these would be very easy to set up and manage and could be run via Jenkins by whoever, whenever it was required.

          Show
          Tim Barker added a comment - This type of testing is very suited to the Selenium test automation suite. I agree with Eloy, to plan a good suite of regression tests I will need a list of UI elements. Without this I cannot build a coverage map or plan yui targeted regression testing properly. If we did this, the regression testing of these would be very easy to set up and manage and could be run via Jenkins by whoever, whenever it was required.
          Hide
          Tim Barker added a comment -

          I performed the following regression testing:
          Run Selenium test suite.
          Performed additional ad-hoc exploratory testing.
          No problems noticed so far.

          Show
          Tim Barker added a comment - I performed the following regression testing: Run Selenium test suite. Performed additional ad-hoc exploratory testing. No problems noticed so far.
          Hide
          Dan Poltawski added a comment -

          Bonza mate!

          Your changes have made it into the Moodle release! Its time to celebrate! Put a shrimp on the barbie and grab a stubby.

          Hooroo

          Show
          Dan Poltawski added a comment - Bonza mate! Your changes have made it into the Moodle release! Its time to celebrate! Put a shrimp on the barbie and grab a stubby. Hooroo
          Hide
          Andrew Nicols added a comment -

          This has caused a regression on master - git bisect points to this commit. Will verify and open a new issue.

          Show
          Andrew Nicols added a comment - This has caused a regression on master - git bisect points to this commit. Will verify and open a new issue.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: