Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overlapping Tests #42

Open
ysiraichi opened this issue Sep 23, 2018 · 0 comments
Open

Overlapping Tests #42

ysiraichi opened this issue Sep 23, 2018 · 0 comments
Assignees

Comments

@ysiraichi
Copy link
Owner

I figured we should, at some point tackle this, since it is kind of annoying. However, laziness had taken over all my time for reporting this issue. We've reached a point where we have some QbitAllocators, whose final mappings are not really obvious. The approach we choose was to establish standard functional tests, while checking whether the semantics and architectural constraints were kept.

That said, they all work. But we all those "standard" tests are overlapping code with only some types different. Thus, I urge for a generalized testing environment for both QbitAllocators and ArchGraphs.

Solution: one I can think of is by calling InitializeAllArchitectures (the same for QbitAllocators), and iterating through the list, testing instantiation, and functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant