You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
I am almost done implementing CPU TopK-1 and am passing the op tests I wrote. However it takes quite a while to write the unit tests, and I feel even if I spent another hour writing tests, I could be missing something.
So I'm thinking I should also write some additional randomized test cases in the folder unittest/cpu (which does not exist). I think this would be more exhaustive and take less time to write more tests. If this sounds okay I will start on it in a few days.
If it is also okay, I'd like to add an option to run one unit test at a time. I would change npm test unittest to npm test unittests, and add an npm test unittest [test], which only runs one unit test. If that is okay, I will also get started on that in the next couple of days.