This shows a testcase for an old caching library that I use for a project. It features simple save/load/delete functions (sadly static calls) but what I want to focus on is the test code written for this class.

Recently we got this great change to show off code, so I'd like to ask you if you can read that testcode, understand what the class might do and how you would improve upon it.

This shows a test case for an old caching library that I use for a project. It features simple save/load/delete functions (sadly static calls) but what I want to focus on is the test code written for this class.

Recently we got this great change to show off code, so I'd like to ask you if you can read that test code, understand what the class might do and how you would improve upon it.

for starters i though of going with a mostly code only example.

This shows a testcase for an old caching library i use for a project. It features simple save/load/delete functions (saidly static calls) but what i want to talk about is the test code written for this class.

In my opinion the Unittests for a class show of how all functions of a class work and what to expect from that class.

So since we got this great change to show off code i'd like to ask you if you can read that testcode, understand what the class might do and how you would improve upon it.

This shows a testcase for an old caching library that I use for a project. It features simple save/load/delete functions (sadly static calls) but what I want to focus on is the test code written for this class.

In my opinion the unit tests for a class should show how all functions in the class work and what to expect from that class.

Recently we got this great change to show off code, so I'd like to ask you if you can read that testcode, understand what the class might do and how you would improve upon it.