discord-bot/Tests
2020-02-07 16:03:25 +05:00
..
Test Files Test project 2018-11-05 19:33:30 +05:00
IrdTests.cs better azure pipelines integration and building docker image 2019-09-19 23:32:05 +05:00
LogParsingProfiler.cs test for log analysis profiling 2019-11-01 00:05:54 +05:00
readme.md some docs 2019-04-01 22:52:27 +05:00
StarsFormatTest.cs better azure pipelines integration and building docker image 2019-09-19 23:32:05 +05:00
StringUtilTests.cs tweak some zalgo stripping and filter stripping of strings 2019-12-01 19:04:49 +05:00
Tests.csproj update dotnet deps 2020-02-07 16:03:25 +05:00
TimeParserTests.cs better azure pipelines integration and building docker image 2019-09-19 23:32:05 +05:00
ZalgoTests.cs refactor to use using statement whenever it makes sense 2019-11-25 18:07:01 +05:00

Tests

I am using NUnit, mostly because I'm most familiar with this test framework. There's not a lot of tests for the code itself, it is mostly used for testing things out before implementation.

You can use the regular $ dotnet test command to run the tests without any additional tools.

If you want to contribute new test code, I have a couple of preferences:

  • Do use Assert.That(expr, Is/Does/etc) format instead of deprecated Assert.AreEqual() and similar.

  • Try to write the code in the way that does not require the use of InternalsVisibleTo attribute.

  • Tests that require any external data that must be manually supplied, should be disabled by default.