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

Convert unit tests to NUnit 4.0 #259

Conversation

dodexahedron
Copy link
Contributor

Opening this PR now, to provide easy tracking of work done on this back at the master repo.

This is not ready for merge at this time, though you are certainly free to merge whenever and as often as you like. I'll change this from draft status when the work is done.

dodexahedron and others added 19 commits December 2, 2023 15:55
Pushing so I can switch computers
Conversion to Constraints for #1
Added a couple of assertions for #2
A couple of Assumptions for #3
A few Assert.Multiples for #4
Takes care of 2 inspections VS was throwing
Replaces GetArray
Using framework naming convention for methods that return boolean status and have out parameters that are non-null on success
There's another use of the old method, but I have to stare at it a bit more to see what it's really doing.
Might need to discuss that one when we chat.
…o convert-tests-to-constraint-model

Interim merge for #15
There's more to be done, but I'm going to get back to test conversion for a bit, now that several of the loudest issues are addressed
@tznind tznind deleted the branch gui-cs:v2_latest_changes_pre_220 December 3, 2023 10:59
@tznind tznind closed this Dec 3, 2023
@tznind
Copy link
Collaborator

tznind commented Dec 3, 2023

Hey sorry for this, looks like it closed when I merged v2_latest_changes_pre_220 into v2

Can you please re-open and target v2 branch? This is great work!

@dodexahedron
Copy link
Contributor Author

No problem.

Will do when I next touch it, probably later today.

Since I'll be rebasing, I'll probably squash a few commits, in the process.

Just FYI in case you happen to have checked any of it out, since there will be force pushes.

@tznind
Copy link
Collaborator

tznind commented Dec 5, 2023

Cool, let me know when it is ready <3

@dodexahedron
Copy link
Contributor Author

Opening up a new one, shortly.
Lots more improvements since the last one.

This one includes some commits under the src folder, mostly for formalizing a couple of things and also for adding new stuff, as part of a gradual process to eliminate some reflection, where possible.

A lot of tests have been unrolled into unique cases, and some tests are much more thorough, now (especially in the CodeDomArgsTests class).

All tests pass, and the tested cases are a superset of cases that were previously tested.

I would suggest not merging, yet, as I have some incomplete in-progress modifications happening to the github workflows to make them leaner and give us better control over them. We should probably chat about that stuff at some point, too, to be sure the final behavior is as desired.

@dodexahedron
Copy link
Contributor Author

Here ya go

Opened #260

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.

2 participants