Skip to content

[TEST-BUG] - Tests don't validate behavior of all targets #57

@smaillet

Description

@smaillet

.NET Framework Used:

  • .NET 9.0
  • Something else

OS Environment:

  • Windows 10
  • Windows 10 IoT Core
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

OS Version: ####.####...

I have already...

  • Reproduced the problem using the latest stable release.
  • Reviewed the documentation.
  • Reviewed the current issues to check that the issue isn't already known.

Description:
Ubiquity.NET.Versioning.Build.Tasks.UT does NOT validate all of the targets. It only validates the creation of the version information but does not validate anything that depends on that. (Example, generation of version info header for native code, or Assembly Info for legacy) The latter is questionable and may be worth considering elimination
as SDK based projects CAN target the older frameworks.

Steps to reproduce the problem:

  • Reviewed the documentation.
  • Included Sample code or link to repository/gist to reproduce the bug (This is the fastest way to a resolution as it reduces the time to reproduce the problem. The smaller the sample is the better.)

Run the testsm examine source - they don't validate these features.

Expected Behavior
All supported features/functionality is tested.

Actual Behavior
Not tested, just assumed OK...

NOTE:
Generated headers are validated and used in other repositories, so it is not like it is completely unknown. It is just that there are no formal tests to verify things before they become an issue elsewhere.

Metadata

Metadata

Assignees

No one assigned

    Labels

    TestTest related itembugReported as a bugenhancementFeature additional or other Design Change Request (DCR)

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions