1864: Integration tests for Verein360 applications #1879
Conversation
…egration-tests-for-addeakapplication
seluianova
requested review from
steffenkleinle,
f1sh1918 and
ztefanie
as code owners
|
|
||
| companion object { | ||
| @JvmStatic | ||
| fun validationErrorTestCases(): List<ValidationErrorTestCase> { |
There was a problem hiding this comment.
i would add here the policy opt in
givenInformationIsCorrectAndComplete to check that its set
Import is also a test if personalData like name and the contactName in organization data is set
There was a problem hiding this comment.
I will open a separate PR for that, it requires some additional work
There was a problem hiding this comment.
The problem with these fields is that they are validated in init blocks, which means, it's not possible to create an application object with invalid values, such as givenInformationIsCorrectAndComplete = false.
I think I would have to re-work the current approach and build an application as a string rather than as an object.
Or create a default object, serialize it to a string, and then replace the values in the string with invalid values.
Not sure yet what is less ugly.
I will create another task for that.
UPD. or will just re-open and update the description of the current one
| * Serialize object into graphql request format | ||
| * e.g. { stringProperty: "value", intProperty: 123, objectProperty: { booleanProperty: true } } | ||
| */ | ||
| fun serializeObject(obj: Any): String { |
Short description
Integration tests for Verein360 applications
Proposed changes
Not included:
Side effects
no, only tests
Testing
n/a
Resolved issues
Fixes: #1864