[MGNLUI-245] Testing: add test for configuration by code Created: 27/Nov/12  Updated: 03/Dec/13  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia UI
Component/s: framework, testing
Affects Version/s: 5.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Espen Jervidalo Assignee: Mikaël Geljić
Resolution: Obsolete Votes: 0
Labels: configuration-by-code, framework
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

ui-model conf-by-code went into ui-model and decreased the threshold dramatically

We should test the functionality but not that calling of the setters.



 Comments   
Comment by Philipp Bärfuss [ 29/Nov/12 ]

We should check that we are not testing POJOs.

Comment by Mikaël Geljić [ 03/Dec/13 ]

Tentatively closing since configuration by code was removed, then reintroduced since then. It's the responsibility of such tasks to provide decent tests. And as stated, most builders are dead-simple collections of accessors to definition setters.

Idea: builder tests should however match configuration possibilities at all time, so perhaps it would make sense to have a base test class for these builders, based on reflection against their corresponding definition class.

Generated at Mon Feb 12 08:35:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.