Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test/172 geometry engine tests #173

Merged
merged 4 commits into from
May 19, 2023
Merged

Conversation

TimPurdum
Copy link
Collaborator

Closes #172

I created a new project, dymaptic.GeoBlazor.Core.Test.Blazor. This is a Blazor Server app with a few classes that create an in-browser test runner. You can run all tests, all from one class, or one at a time. Success, failure, and stack traces are displayed. You can also tap into ResultBuilder to add text messages to tests, such as JSON output.

I implemented GeometryEngineTests.cs on top of this test runner, which tests all the current GeometryEngine methods (not including the ones in #171).

Future ideas:

  • figure out how to run these tests in an automated pipeline
  • add unit tests for more features

@TimPurdum TimPurdum requested review from seahro and AndersenBell May 16, 2023 01:20
@TimPurdum TimPurdum self-assigned this May 16, 2023
Copy link
Collaborator

@AndersenBell AndersenBell 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

@TimPurdum TimPurdum merged commit d9b9648 into develop May 19, 2023
@TimPurdum TimPurdum deleted the test/172_geometry_engine_tests branch May 19, 2023 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unit Test GeometryEngine
2 participants