Versions Compared

Old Version 13

changes.mady.by.user Gail Steinhart

Saved on

compared with

New Version 14

changes.mady.by.user Felicity Dykas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gail Steinhart Cornell University Library

Felicity Dykas University of Missouri


Apologies


DSpace 7.0 Testathon Planning

  • Tim Donohue and Bram Luyten joined the meeting to discuss the testathon
  • Releases update / Tim
    • Active beta releases have been used to push features out. Beta 5 is the final beta and will include fixes of a lot of bugs.
    • March 17 - QA; complete all development, internal testing, review. The group is on track for this. Between March 17 and the test-a-thon the group will be working to prepare the code for the testing. Work is still being done on configuration entities / database.
    • April 19 - Begin the test-a-thon. The test-a-thon will last three weeks
    • Next week  - would like to announce the test-a-thon
    • A month after the end of the test-a-thon - final release. This will depend on the feedback received during the test-a-thon. If large bugs are found, this date could be 2-3 months after the test-a-thon.
    • See DSpace 7 working group notes for other dates
  • Test-a-thon plans / Bram
    • Bram drafted a test plan spreadsheet. He based it on previous test-a-thons and modified it based on new features.

    • https://docs.google.com/spreadsheets/d/1BdK8SzytA7HoxOZgldCIHabMxeR4mYTXt_ynVT_-KR8/edit#gid=1131720008

    • How DCAT can contribute to tests
      • Write new tests
      • Test
    • Spreadsheet has two tabs
      • Tab 1: Summary
        • Summarizes the state of the execution
        • Links to angular IU ad the Rest UI
        • Angula UI - important. On second tab this is used to build links which will contextualize for one's own repository. So, tests will not need to be done on a local installation. However, if the local installation includes customized workflows it may be useful to ensure that customisations are not broken.
        • Status
          • There are tests for each status.
          • Some indicate that the status is "not applicable," this means that it is not supposed to work for the first release. It will be scheduled for DSpace 7.1 or 7.2. Attendees agreed that it is useful to retain these in the spreadsheet.
        • Date and people testing. The last test and person will be entered here. If re-testing, the original information will be overwritten.
        • Colors
          • Yellow = something is wrong with the test description. Reviewers can mark the test as being unclear.
          • Red = there is a problem with the test and the expected results are not happening. E.g., UI problem.
      • Tab 2: Test cases
        • Each test has a persona and an account associated with it. There is a password for each account. The password is the name of the software.
        • Persona. There is a link for the persona. The link goes to a specific page or homepage.
        • Each test has an ID and feature category.
        • There is an column for expected behavior or results.
        • Th
  • Discussion about the dates
    • Ramadan is from
  • The Testathon is tentatively scheduled to take place the weeks of April 19th, April 26th and May 3rd