[
https://issues.apache.org/jira/browse/ISIS-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-2837:
----------------------------
Description:
Currently kroviz integration tests simply check, if an application is available
at localhost:8080.
Ensure a docker image is running at this address and skip the check.
c.f.
https://info.michael-simons.eu/2016/08/25/integration-testing-with-docker-and-maven/
was:
The state of the model-user interaction is kept in the EventStore. The ES logs
all request/response pairs (LogEntry) and for each holds 1:n relations to
Aggregtators.
An Aggegator may be related to many LogEntries (resulting in m:n in total) and
acts as a facade to the DisplayModel. DM's are rendered by views (RoDisplay).
Incoming updates refresh the views.
For kroviz the scenario you described boils down to: an updated entity may be
part of an additional object list as well (and it's Aggregator/RoDisplay pair).
There needs to be an (additional) relation between certain LogEntries and/or
their Aggregators to handle this .
See:
https://the-asf.slack.com/archives/CFC42LWBV/p1619869133072400?thread_ts=1619867697.070300&cid=CFC42LWBV
> [kroviz] Execute Integration Tests against Docker Image (Demo)
> --------------------------------------------------------------
>
> Key: ISIS-2837
> URL: https://issues.apache.org/jira/browse/ISIS-2837
> Project: Isis
> Issue Type: Improvement
> Components: Isis Client Kroviz
> Reporter: Jörg Rade
> Assignee: Jörg Rade
> Priority: Major
> Fix For: 2.0.0-M6
>
>
> Currently kroviz integration tests simply check, if an application is
> available at localhost:8080.
> Ensure a docker image is running at this address and skip the check.
> c.f.
> https://info.michael-simons.eu/2016/08/25/integration-testing-with-docker-and-maven/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
