26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394
84%
main: 81%

Ran 16 Oct 2023 04:54PM UTC

Jobs 1

Files 187

Run time 15s

Badge

Embed ▾

Committed 16 Oct 2023 04:50PM UTC coverage: 84.061%. Remained the same

Build # 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394

Build Type

Pull #394

github

Committed by

rbino

Commit Message

Check unique name + cluster_id constraint in Realm changeset

This is triggered if someone tries to create a realm with the same name and
cluster in a different tenant. The unique index was already there, this just
avoids raising when the insertion is made.
Add a couple of tests to verify both unique constraints on realm name.

Signed-off-by: Riccardo Binetti <riccardo.binetti@secomind.com>

Pull Request Pull Request #394: Check unique name + cluster_id constraint in Realm changeset

Run Details

1445 of 1719 relevant lines covered (84.06%)

233.42 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394.1	16 Oct 2023 04:54PM UTC	187	84.06	GitHub Action Run

edgehog-device-manager / edgehog / 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394
84%
main: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394

edgehog-device-manager / edgehog / 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394 84% main: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394

edgehog-device-manager / edgehog / 26f7facc2157ad0e6c2465fc66122c210c50a40c-PR-394
84%
main: 81%

README BADGES
x