-
Notifications
You must be signed in to change notification settings - Fork 3
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
Expand testing #4
Comments
Closed
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
#3 Remove explicit support for net6.0
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
…meworks The following line makes it so that tests are run sequentially. This seems to be necessary. If I don't have it, tests seem to fail randomly. I suspect it's related to the IL being rewritten. Should probably look further into it.
Miista
pushed a commit
that referenced
this issue
Jan 12, 2024
Miista
pushed a commit
that referenced
this issue
Jan 13, 2024
Miista
pushed a commit
that referenced
this issue
Jan 13, 2024
Miista
pushed a commit
that referenced
this issue
Jan 13, 2024
Miista
pushed a commit
that referenced
this issue
Jan 13, 2024
Miista
pushed a commit
that referenced
this issue
Jan 13, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need tests for shimming a:
At the same time we could update the tests to a more modern test framework
The "hierarchy" of tests is as follows:Please see alternate hierarchy below.
Note: Assume that all members are public.
2.1 Getters
2.2 Setters
3.1 Methods on any instance
3.2 Methods on specific instance
3.3 Methods on abstract reference type
4.1 Methods on any instance
4.2 Methods on specific instanceThis is not supported! It's only here for completeness sake.5.1 Reference types
5.2 Value types
There is the following alternate hierarchy (which I might be more partial to):
Isolation
These tests exercise the entire library via
PoseContext.Isolate
.Shimming
Note: These tests should be renamed to "Isolation".
These are the full-blown tests which test the entire stack.
We want to test the following:
1.1 Static types
1.2 Reference types
1.2.1 Any instance
1.2.2 Specific instance
1.3 Value types
1.3.1 Any instance
1.3.2 Specific instance of value typeThis is not supported! It's only here for completeness sake.1.4 Abstract methods
1.5 Sealed types (both reference and value types)
2.1 Static types
2.2 Reference types
2.2.1 Any instance
2.2.2 Specific instance
2.3 Value types
2.3.1 Any instance
2.3.2 Specific instance (Is this supported?)
2.4 Sealed types (both reference and value types)
3.1 Static types
3.2 Reference types
3.2.1 Any instance
3.2.2 Specific instance
3.3 Value types
3.3.1 Any instance
3.3.2 Specific instance (Is this supported?)
3.4 Sealed types (both reference and value types)
4.1 Static typesNot currently possible4.2 Reference types
4.3 Value typesIt seems this isn't supported4.4 Sealed types (both reference and value types)
Method rewriting
These tests should only be concerned with rewriting methods.
We wants to test for:
IL generation (via stubs)
These tests are concerned with generating IL for stubs (which will later be used to inject the shims).
We want to test that we can generate stubs for:
Other
These tests I have not been able to put into any specific category. They are therefore lumped together here.
We want to test the following:
The text was updated successfully, but these errors were encountered: