Page tree
Skip to end of metadata
Go to start of metadata

Date & Time

  • March 9th 16:00 UTC/GMT - 11:00 EST

Zoom meeting:

We will be using the DSpace Zoom Meeting Room for our meeting.

Meeting location: 

Join from PC, Mac, Linux, iOS or Android: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040) Passcode: dspace

  • Or via Telephone: Dial (for higher quality, dial a number based on your current location), Passcode: 995571
    • USA: +1 669 900 6833 or +1 408 638 0968 or +1 646 876 9923 
    • Australia: +61 (0) 2 8015 2088 
    • Belgium: +32 (0) 2 588 4188 
    • Brazil: +55 11 4680 6788 or +55 21 3958 7888 
    • Canada: +1 647 558 0588 
    • Czech Republic: +420 2 2888 2388
    • Finland: +358 (0) 9 4245 1488
    • France: +33 (0) 1 8288 0188 
    • Germany: +49 (0) 30 3080 6188 
    • Ireland: +353 (0) 1 691 7488
    • Italy: +39 069 480 6488 
    • Netherlands: +31 (0) 20 241 0288
    • New Zealand: +64 (0) 4 831 8959 or +64 (0) 9 801 1188 
    • Norway: +47 2396 0588
    • Portugal: +351 308 804 188 
    • Spain: +34 91 198 0188
    • United Kingdom: +44 (0) 20 3695 0088 
    • Additional international numbers available at https://lyrasis.zoom.us/zoomconference?m=YzSC5pcRHDJ1so3QBrCCg3FS96Uskzw3
  • Enter Meeting ID: 502 527 3040 , followed by #

Zoom information: DSpace Meeting Room

Agenda:

  • DSpace 7.0 Testathon Planning (Tim Donohue and Bram Luyten will join the meeting)
    • The Testathon is tentatively scheduled to take place the weeks of April 19th, April 26th and May 3rd
    • Draft DSpace Release 7.0 Testathon Page 

    • Draft DSpace 7.0 test plan
    • Planning announcements for Testathon (Marketing Group?)

Preparing for the call

If you can join the call, or are willing to comment on the topics submitted via the meeting page, please add your name, institution, and repository URL to the Call Attendees section below.  

Meeting notes


Call Attendees

Maureen Walsh The Ohio State University Libraries

Bram Luyten (Atmire) 

Mariya Maistrovskaya University of Toronto

Iryna Kuchma EIFL 

Jere Odell IUPUI

Anne Lawrence Virginia Tech

Gail Steinhart Cornell University Library

Felicity Dykas University of Missouri

Tim Donohue 

Jennifer Bielewski


Apologies


DSpace 7.0 Testathon Planning

  • Tim Donohue and Bram Luyten joined the meeting to discuss the testathon.
  • Dates and updates on releases / 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 testathon 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 testathon. The testathon will last three weeks
    • Next week  - would like to announce the testathon
    • A month after the end of the testathon - final release. This will depend on the feedback received during the testathon. If large bugs are found, this date could be 2-3 months after the testathon.
    • See DSpace 7 working group notes for other dates
    • Draft DSpace Release 7.0 Testathon Page 
    • Discussion about the dates
      • Ramadan is from April 13-May 12. The testathon dates are problematic.
      • Easter is April 4.
      • Tim will take this to the DSpace meeting. It may be possible to push the dates back a week.
  • testathon plans / Bram
    • Bram drafted a test plan spreadsheet. He based it on previous testathons and modified it based on new features.
    • https://docs.google.com/spreadsheets/d/1BdK8SzytA7HoxOZgldCIHabMxeR4mYTXt_ynVT_-KR8/edit#gid=1131720008

    • Spreadsheet - has two tabs
      • Tab 1: Summary
        • Summarizes the state of the execution
        • Links to Angular UI and the Rest UI
        • Angular 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 customizations 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.
        • 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 a column for expected behavior or results.
      • Discussion about spreadsheet
        • Previous tests had a field for Jira. All agreed that this will still be useful. It is a way for testers to see information on the feature and issues reported. Bram added a column for github, where this information is now stored.
        • Comments: Add details about the testing here. The team will follow the comments and will add the information to tickets. Issue templates. These are used by the Team. More data is added than is found in the spreadsheet to all the Team to sort issues.
        • Access to spreadsheet. Attendees discussed whether the spreadsheet should be open to all for viewing and editing. Decision: lock content that will not need to be modified and make it editable by all. Bram will make a backup of the original.
    • Test workflow
      • Enter data and name or nickname; enough information so that you can be contacted.
      • Add test status.
      • Add comments to provide further information.
      • If something is tested prior to the testathon, it should be retested, and the information updated. Retesting is needed as the team may have made changes up until the testathon.
      • Retesting: The last test and person will be entered here. If re-testing, the original information will be overwritten. The spreadsheet has versioning, so previous entries can be accessed.
      • Discussion about workflow:
        • Previous tests were different than this one, as the features were familiar to testers. DSpace 7 has new features. DCAT 7 will need help in created scenarios.
          • Look at DSpace 7 documentation (though it is not updated)
          • Do what you can and add comments to the spreadsheet.
          • Contact Tim. He indicated that he will be glad to answer question and to review test scenarios. Ping him on Slack.
      • Other tests
        • Invite people to test out installation instructions. Oracle database, etc. These may need to be described on the testathon page.
    • Bram will create a video about the test plan.
    • How DCAT can contribute to tests
      • Write new tests / scenarios
      • Test

DCAT news

  • DCAT will delay its next user documentation sprint
  • Maureen (chair) will send out an email to ask for volunteers to help with the testing

Meeting notes by Felicity





  • No labels

2 Comments

    1. now publicly available under http://bit.ly/dspace-7-test-plan 

      Edit rights can be requested by anyone who wants to work on adding more tests

      Edit access will be completely public during the testathon.