Show threadÆnðr E. FeldstrawApr 28, 2019
Seriously, what the heck, #Microsoft #Windows? First you tell me you can't access the drive letter, and then when I map it you tell me it's there already? You suck at #accessPrivileges.

Final solution: unmap the drive letter, and then in the #MSDosBatch script first map it, then unmap it when done.

Holy moly, Gates et al, did you have to make your system contradict itself? - 4/4
Show threadÆnðr E. FeldstrawApr 28, 2019
What the heck are you doing, #Microsoft #Windows?

At my wit's end, I have an idea. Maybe I can have the #MSDosBatch script create the drive letter so it will be available during the #ScheduledTask session? Yes, I can! With the #NetUse command.

On first try: fail! Drive letter already is mapped - 3/4
Ænðr E. FeldstrawMar 1, 2019
Today I was #unitTesting some #predicate script (#MSDosBatch), that I thought to be easy and straightforward.

I was wrong.

The script returned both a boolean true and a boolean false for any and all input.

To catch this, your suite of unit tests MUST include negative tests, that answers questions like:
- does it return exactly 1 result, and no more?
- does it return the negative result when given a known negative input?