yes,
I'm just measuring the correctness: my performance now are reasonable ( in term of move generation ) for a C# program as mine: I can't beat the HG Mueller qperft, neither the "emptran" shown in the Steven Edwards post, but is competitive in term of speed with some other engines I found, even in C++.
This obsession for testing correctness derive from my previous engine: I was unexperienced, and I created a slow and buggy move generator, I had a TT as well, but who can trust without a solid testing fundation ? So I ended in avery poor job, in an untestable search and a very uncompetitive engine.
I did not find any other way to probe if TT is working correct than challenge it on a perft session.
This appear to be tricky as well, because a big testing with a lot of position, but ending at perft 6 was perfectly working, to discover errors I had to go down to perft 9, and I'm still not sure on what will happen at perft 10