Testability - introduce own odata v2 target service for integration testing

Open
#69 1 comment 0 reactions 1 assignee View on GitHub

@phanak-sap is already working on this.

Since Aug 28, 2020.

Assessment

This issue has not been assessed yet.

Description

It should be possible to use this project (other than Java Olingo) - https://github.com/htammen/n-odata-server

Rationale. for V4 we will use SAP CAP framework for similar, it will never support Odata V2 and n-odata-server, even unmaintained, seems to support what is needed to have service parseable by pyodata - valid metadata etc.

  • Should be able to support different test case scenarios (e.g. $metadata), ideally by different URL so it is self-documented in the python part of code
  • Dockerized. At the moment not sure if it is better to run as "swarm" in two containers or different testing dockerfile for python+nodejs together.

Relevant issues:

  • #46
  • Controlled randomness for entire odfuzz. It may be worth to have integration test deterministic for regression prurposes, therefore entire odfuzz must start with input for random.seed(), as currently used in unit tests (TODO new issue, #46 is not covering this requirement)
Dominant language
Python
Stars
23
Forks
12
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SAP/odfuzz

All issues in SAP/odfuzz

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.