Noise from the Basement

Today, July 28th, 2023, is System Administrator Appreciation Day. A day I didn’t know existed until now but has been around since 2000.

It was during one of my first paid technical positions that I realized that sys admins, and other support staff including non-technical, can be a thankless job. A job where your only interactions with others is when something goes wrong.

During university I had a summer job as a Systems Analyst Trainee at TELUS Advertising Services (TAS). TAS was division of TELUS that created the phone books, both white (residential) and yellow (businesses) pages. I did typical IT tasks at the time such as setting up new computers with token ring network cards and helping staff issues such as accessing email. Also lots of printer issues.

I, Chris, try to add a system test for the todo bug fix in episode 5 but run into some issues. I find out I stupidly hard coded the todo file name when he first added the ability to generate a todo file in Standard. When recording this video I think that is why his system test doesn’t work but upon re-watching this video I have my doubts. Only time will tell if my doubts are correct or not.

I’m happy to announce that NConstraints v1.1.1 has been released! This release updates the NuGet package from .NET Standard 1.6 to 2.0 and should work with all versions of NUnit 3.

You can install NConstraints via the dotnet command line:

dotnet add package SaturdayMP.NConstraints --version 1.1.1

Other install options can be found here.

NConstraints currently only has one constraint called EquivalentPropertyWiseTo. It checks if all the property values on two objects are the same. Instead of writting:

[Test]
public void TestObjectsTheSame()
{
  var expected = new ExpectedClass() { ValueOne = 1, ValueTwo = "Blah", ValueThree = 33 };

  var actual = MethodBeingTested();
   
  Assert.That(expected.ValueOne, Is.EqualTo(actual.ValueOne));
  Assert.That(expected.ValueTwo, Is.EqualTo(actual.ValueTwo));
  Assert.That(expected.ValueThree, Is.EqualTo(actual.ValueThree));
}

You can write:

I add a unit test for the Standard Ruby linter bug fix done in the last episode. When adding the unit test I find out someone has improved the todo generation logic. Thank you. I also find a remove a redundant test.

Read about the bug being fixed here.

In this episode I implement a fix for the todo file generation bug in the Standard (Ruby linter) and do some manual testing. Also use ChatGPT to explain some code that GitHub Copilot generated.

Read about the bug being fixed here.

See the previous episode, number 4, where I create I duplicate the issue and come up with the fix possible fix.