loafle/openapi-generator
3
0
Fork 0
forked from loafle/openapi-generator-original
Code Pull Requests Activity
openapi-generator/samples/openapi3/client/petstore/dart2/petstore
History
Peter Leibiger 4ad6d0bfe5
[dart] Variable/Operation/Model naming (#8123) 
* [dart] Properly escape param/var names that clash with Dart types

* [dart] Add tests for var/enumVar names

* note: public and private are no keywords in Dart
* some tests are still wrong, some are commented out

* Fix typo

* [dart] Improve variable name escaping

* add more tests

* [dart] Fix operationId naming

* [dart] Fix upper case var name with leading underscore

* [dart] Correctly support model prefix/suffix

* [dart] Support spaces in property names

* Call super for empty operationId

* [dart] Fix and improve enumVar naming/generation

* use same handling for all 3 generators
* allow `updateEnumVarsWithExtensions` to have access to the data type
* improve `x-enum-values` handling and add supprt for other enum vendor extensions
* remove duplicate and outdated tests from `DartDioModelTest`
* add more tests to `DartModelTest`
* no longer force lowercase enums for plain dart generator (breaking)
* this change also removes the trailing underscore from plain dart generator (breaking)
2020-12-09 23:21:08 +08:00
..
test
[dart] Variable/Operation/Model naming (#8123)
2020-12-09 23:21:08 +08:00
.analysis_options
[dart] Cleanup and OAS3 support (#8085)
2020-12-07 21:38:39 +08:00
pom.xml
[dart] Cleanup and OAS3 support (#8085)
2020-12-07 21:38:39 +08:00
pubspec.yaml
[dart] Cleanup and OAS3 support (#8085)
2020-12-07 21:38:39 +08:00
README.md
[dart] Cleanup and OAS3 support (#8085)
2020-12-07 21:38:39 +08:00

README.md

Background

Current state of tests

TL;DR currently the only tests are e2e tests that were adapted to use a faked http client. While pushing data around as a smoke test has some value, more testing is required. In particular we need comprehensive unit/integration tests.

  • an old set of e2e tests are skipped for CI, as they hit a live endpoint and so are inherently flaky
    • pet_test.dart
    • store_test.dart
    • user_test.dart
  • the above set of tests were adapted to use a faked http client
    • the tests are not really well suited to being used with a stubbed client, many are basically just testing the endpoint logic
    • while not a great set of tests, they do have some value as a smoke test for template changes
  • the adapted tests and files that contain test data:
    • pet_test_fake_client.dart
    • store_test_fake_client.dart
    • user_test_fake_client.dart
    • fake_client.dart
    • file_upload_response.json

Assumptions

  • the tests will be run as part of CI and so have access to dart:io

Running

If not already done, resolve dependencies

pub get

To run tests in a single file:

pub run test test/pet_test.dart

To run all tests in the test folder:

pub run test