Skip to content

Add verification and pass history to seed data

Alex requested to merge verification-history-seed-data into master

Part of #738

What does this MR do?

The seed data did not include any verification and pass history yet. This adds 3 of them to each user.

How confident are you it won't break things if deployed?

very sure

How to test

  1. Checkout branch locally
  2. Run ./scripts/seed
  3. Login as userorga
  4. Go to any user's profile
  5. Open the verification history and pass history in the menu on the left
  6. There should be some entries

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • used "state:" labels to track this MR's state until it was beta tested
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) (for: Dev)
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text in German

Merge request reports