[GH-ISSUE #22] Add Unit Tests #14

New issue

Open

opened 2026-02-26 10:35:14 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 10:35:14 +03:00

Owner

Originally created by @Pro on GitHub (Mar 13, 2014).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/22

Add Unit Tests (usable by Travis CI) to test functionality of Signing, Regex, Configuration Errors....

Originally created by @Pro on GitHub (Mar 13, 2014). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/22 Add Unit Tests (usable by Travis CI) to test functionality of Signing, Regex, Configuration Errors....

kerem added the

enhancement

agent

labels

2026-02-26 10:35:14 +03:00

kerem commented

2026-02-26 10:35:14 +03:00

Author

Owner

@Pro commented on GitHub (Aug 20, 2014):

https://github.com/thelinuxlich/artemis_CSharp/blob/master/.travis.yml
http://stackoverflow.com/questions/16751772/how-do-i-use-travis-ci-with-c-sharp-or-f

@Pro commented on GitHub (Aug 20, 2014): https://github.com/thelinuxlich/artemis_CSharp/blob/master/.travis.yml http://stackoverflow.com/questions/16751772/how-do-i-use-travis-ci-with-c-sharp-or-f

kerem commented

2026-02-26 10:35:14 +03:00

Author

Owner

@AlexLaroche commented on GitHub (Nov 20, 2014):

http://www.codeproject.com/Articles/3781/Test-Driven-Development-in-NET

@AlexLaroche commented on GitHub (Nov 20, 2014): http://www.codeproject.com/Articles/3781/Test-Driven-Development-in-NET

kerem commented

2026-02-26 10:35:15 +03:00

Author

Owner

@Pro commented on GitHub (Nov 20, 2014):

It would be nice to add different emails each in a txt file (in Mime format) into a subdirectory within the test directory. During unit test those all email files from within this directory should be signed and the resulting signature be validated against the known value and public key.

@Pro commented on GitHub (Nov 20, 2014): It would be nice to add different emails each in a txt file (in Mime format) into a subdirectory within the test directory. During unit test those all email files from within this directory should be signed and the resulting signature be validated against the known value and public key.

kerem commented

2026-02-26 10:35:15 +03:00

Author

Owner

@AlexLaroche commented on GitHub (Nov 22, 2014):

We should start by implement test on each function. After that to implement tests on the whole application. If some class depend on other we should use mock as decribe in the article I have posted previously.

Screenshot of interface to see the results of the tests. I have seen some scripts to do this in travis.

@AlexLaroche commented on GitHub (Nov 22, 2014): We should start by implement test on each function. After that to implement tests on the whole application. If some class depend on other we should use mock as decribe in the article I have posted previously. Screenshot of interface to see the results of the tests. I have seen some scripts to do this in travis. ![image](https://cloud.githubusercontent.com/assets/5282389/5155175/26900f38-724a-11e4-8dc4-8f9f729e7643.png)