This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Add real-world code #16
Labels
enhancement
[issue/PR] requests / implements new or improved functionality.
Reference version
2.0.1-preview
Background and motivation
If we want procedures like testing and coverage, once implemented and tested here, to be suitable for at least the majority of real-world projects, we need some "real" code to test.
For starters, there is no meaningful way to "arrange, act, assert" when testing parameterless methods that always returns the same constant. But it's more complex than this. We should be able to meaningfully test Coverlet exclusions, determine whether we need some sort of per-project testing customization vs. a one-size-fits-all
default.runsettings
file, and the list grows longer with each hour I spend on this.Proposed enhancement
AaaLib should contain some real-world, or at least real-world-like, code.
It should also contain different kinds of projects:
Once we have projects of different kinds to work on, we will also be able to add e.g. integration tests as briefly suggested in #10.
Implementation proposals
Code can be brought in from tutorials found on the web, at least initially.
Also, with all due respect to the late Douglas Adams, the
Aaa
class has to go. It was good as a first, minimal example to start building Cake scripts and GitHub workflows, but once we have "real" code, it has no place here any longer.Usage examples
n/a
Risks
Of course the removal of the
Aaa
class is a breaking change. I don't expect much customer impact, though, asAaaLib
was never meant to be actually used as a dependency.Additional information
No response
The text was updated successfully, but these errors were encountered: