Uploaded image for project: 'Community Linux Engineering'
  1. Community Linux Engineering
  2. CLE-2965

Private Issues: Unit tests for code ⇔ DB boundary

SetAsigneesSync from "Extern...update-metadata-from-f...XMLWordPrintable

    • 2

      Original reporter: nphilipp@redhat.com

      The issue:

      1. Story

      As a Forgejo upstream maintainer,
      I want that storage and retrieval of private issues in the database is tested thoroughly,
      so I can sleep better at night.

      1. Acceptance Criteria

      Tests exist which verify that …

      • [ ] ­… public and private issues can only be stored through their respective types (`Issue` and `PrivateIssue`) into their respective tables (`issue` and `private_issue`), when inserting and updating entries.
      • [ ] … public and private issues loaded from their respective tables have `IsPrivate` set appropriately.
      1. Background

      https://codeberg.org/forgejo/design/issues/2#issuecomment-8405379

              Unassigned Unassigned
              cle_bot CLE bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: