OData / OData/ODataConnectedService
E2E testing infrastructure
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 84
- Forks
- 52
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 7
Description
While we do have tests to verify that the generate code looks as expected and compiles without errors, we don't have tests to verify that the code we generate runs as expected. We achieve that using manual testing, which is tedious and not enforced. We should consider setting up automated E2E testing to automate catching issues that we can currently only detect via manual testing.
For example, an E2E test could run the CLI to generate client code based on some schema and settings, add a predefined Program.cs file that calls the generated client code against some test OData service, and verify that the code ran as expected by inspecting the program output.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing generated-code and compilation tests, then trace how the CLI generates client code. Define the scope for running a generated client from a predefined Program.cs against a test OData service and checking its output; done means automated tests cover behavior currently verified manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100