Skip to content

Conversation

@LibbyShihh
Copy link
Member

@LibbyShihh LibbyShihh commented Mar 26, 2025

Closes #2

- Implemented abstract test A.1.1 and its integration test (IT)
- Added test URL for execution
- Defined execution order
…variables

- Updated test suite from Features to Maps to fix mvn build error
- Modified testng.xml
- Replaced hardcoded test counts with variables to prevent build failures due to mismatched results
@dstenger dstenger added this to CITE Mar 27, 2025
@github-project-automation github-project-automation bot moved this to To do in CITE Mar 27, 2025
@dstenger dstenger moved this from To do to In progress in CITE Mar 27, 2025
public void verifyMapResponse() throws Exception {
List<URL> urls = MapUtil.fetchMapUrls(rootUri);

for (URL url : urls) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looping over all the map URLs can take up a lt of resources for services with many maps/collections. I'd suggest using the noOfCollections parameter as done in the ets-ogcapi-features10.

Copy link

@bpross-52n bpross-52n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, the code just needs to be formatted mvn spring-javaformat:apply. See also my comment in the MapResponse.java class.

- Resolve formatting violations
- Add noOfCollections to limit test execution

Closes #2
@ghobona
Copy link

ghobona commented Sep 29, 2025

  • @ghobona To check the formatting issues mvn spring-javaformat:apply

@ghobona ghobona assigned ghobona and unassigned dstenger and bpross-52n Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

A.1.2. Abstract Test for Requirement Map Response (Abstract test A.2)

4 participants