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

Unit tests #7

Open
woodruffw opened this issue Nov 2, 2019 · 3 comments
Open

Unit tests #7

woodruffw opened this issue Nov 2, 2019 · 3 comments
Labels
C:tests enhancement New feature or request

Comments

@woodruffw
Copy link
Member

It'd be nice to have some basic tests in the CI, probably using mishegos's manual mode to feed some simple inputs in.

@woodruffw woodruffw added the enhancement New feature or request label Nov 2, 2019
@woodruffw woodruffw self-assigned this Nov 2, 2019
@woodruffw
Copy link
Member Author

To elaborate: we probably want simple valid instruction samples to test with, just to ensure that every decoder reports correctly. Even just some NOPs and simple MOVs would probably suffice.

@woodruffw woodruffw removed their assignment Jan 2, 2020
@woodruffw woodruffw changed the title Unit/regression tests Unit tests Jan 6, 2020
@ekilmer
Copy link
Contributor

ekilmer commented Jan 4, 2022

This would be nice to catch simple runtime issues like missing symbols, even if the workers seem to build correctly (relevant PR for bddisasm bitdefender/bddisasm#53, but this could have easily been any other tool)

@woodruffw
Copy link
Member Author

Yep! It should be very easy to write a basic self-test, since it's just:

M=1 mishegos ./workers.spec <<< "90" > /dev/null

...or something similar, where 90 is the hex string for the instruction to test all of the workers against.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:tests enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants