Skip to content

Conversion of unit tests to NUnit's Constraint model #258

Description

@dodexahedron

The old classic assertion style has been deprecated for quite a while, now, and NUnit 4 takes that a step further by actually moving them off to a separate project and namespace.

I've been working on converting the tests to the new model, in my repo.

I branched from your latest v2_latest_changes_pre_220 branch commit and work is going into convert-tests-to-constraint-model on my repo. I'll open up a PR at some point for easier tracking of what's going on, as work is done.

But I did have a couple of questions about TerminalGuiDesigner for you, @tznind , that came up as I have been going through the tests.
I'd like to chat with you at some point, when you have some time, both to get some clarity on a couple of questions as well as to bounce some ideas off of you regarding something it looks like I might be able to help out with - I just need to be sure I understand it properly before I go any further down that rabbit hole (which isn't that deep, but I want to be sure the intent and result is the same).

I've created a project and issues over at my fork to track the work.

Project: Migration to NUnit 4

Main conversion issue: dodexahedron#1

Branch for conversion work: https://github.com/dodexahedron/TerminalGuiDesigner/tree/convert-tests-to-constraint-model

I'm opening this issue up over here mostly as a placeholder to indicate and link to work being done.
I'll file other issues related to it over there, since it's likely to get a bit noisy.

If you have any thoughts, requests, ideas, commentary, concerns, or whatever, just hit me up over there. :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions