Bug 47113 – Check tests in 67_udm-dns and make them more lightweight

Bug 47113 - Check tests in 67_udm-dns and make them more lightweight


Summary:	Check tests in 67_udm-dns and make them more lightweight

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	DNS
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-06-01 11:15 CEST by Arvid Requate
Modified:	2018-06-01 11:15 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2018-06-01 11:15:34 CEST

We should check the tests in 67_udm-dns if they do what they claim and improve them to make them more streamlined. For example:

  67_udm-dns/106_dns_txt_record_check_resolve

doesn't test UDM dns/txt_record at all, it just adds the 'txt' property of a forward zone.

Also, each and every test in that directory seems to create it's own dummy forward zone just to test if an MX record can be created. And then there ist the next test that checks if an MX record can be modified. That's total overkill and accumulates test time costs.