-
Notifications
You must be signed in to change notification settings - Fork 102
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
Is RegTester.py up2date? #38
Comments
There's no collection of hives and associated .reg files at the moment. Its a great idea though! Do you have access to any examples that you'd be willing to share? |
For now only minimal set of BCD files, but it is better then nothing. |
Sounds good. I'll collect a set of files that I don't mind exposing to the web and upload them as you suggested. |
Willi we should make the hives part of our unified testing |
Yes, I agree. I'd like to collect the .reg and original hives, and export them test dump format for all of them, too. |
I agree as well, an automated unit test for all available hive/reg combos. |
let me know when you are ready and i can make sure you have the latest versions of the updated export format. it should be on google drive as well. |
@NiKiZe surely there are some, but i'm not familiar with any enough to instinctively pick one. I'd welcome suggestions. |
Sorry, I have not yet had time (or maybe it's more a lack of ideas) to do much on this :/ However came across some interesting things in reg.exe a python script running on windows could be used to automate an multitude of tests (or even an cmd script in windows to collect data and then running the python part on any OS) I think what we have suggested for now is walking all .hive files in testing/resources, and using (same named) .reg files call RegTester and make sure the result is as expected. |
RegTester does not seem to be updated to work with current code. Is it used to test changes to make sure everything works?
Is there any archive with Hive files and corresponding .reg files that can be used for regression testing?
Would it be appropriate to have small file sets in the repo for testing?
Have some work on an updated version and will prepare a PR after some sleep.
The text was updated successfully, but these errors were encountered: