none
tests with the term (certification) in their names RRS feed

  • Question

  • Hi,

    Maybe this question is already being asked and answered before...

    I am wondering why same tests are with (certification) in their name and same are not.

    My goal is to get some drivers sighed.

    Am I required to run all the tests list by HCK?

    Thanks,

    Jason

    Wednesday, January 30, 2013 10:00 PM

Answers

  • "(certification)" is a naming convention that some teams used in the tests that are shipped with HCK. However, it has no bearing on which tests need to be run for your particular device or system. More specifically, all tests that are detected for your target will need to be run.
    Thursday, January 31, 2013 1:05 AM

All replies

  • "(certification)" is a naming convention that some teams used in the tests that are shipped with HCK. However, it has no bearing on which tests need to be run for your particular device or system. More specifically, all tests that are detected for your target will need to be run.
    Thursday, January 31, 2013 1:05 AM
  • To run your product for certification.  Here are 10 easy steps from start to finish for you.

    1. Open the HCK Studio (Assuming you have a controller installed, Client connected and studio installed)

    2. Create a New Project (A Project can contain multiple submissions of a family or just 1)

    3. Choose second tab Selection and select the Machine pool your system is in.  Select your Hardware from the list shown or choose another category from the hardware devices category on where it may be found (default is Device Manager category)

    4. Select test Category.  Here you will have your test list to run.  Make sure to run and pass all tests.

    5. Results tab to view results if you need to see a log of why a test is failing.

    6. Package tab.  Here you add drivers and create your package to be sent to Microsoft (Please note Create Package button is far bottom right)  Once you hit create package it will ask you if you wish to sign the package you will need a verisign ID to get it signed and need that key also matching the WHQL account you made with Microsoft. 

    7. Login to https://sysdev.microsoft.com.  Go to "create HCK Submission" and upload your HCK xml and then log file.

    8. Wait for Microsoft to review your submission and you will receive a pass or fail (hope for the best!)

    9. On pass, download your new Cat files.

    10. Drop and replace your old company signed or test signature cat files with your new WHQL signed cat files.

    Presto Done.

    • Proposed as answer by JB-Matrox Thursday, January 31, 2013 3:12 PM
    Thursday, January 31, 2013 3:12 PM
  • Thanks!
    Thursday, January 31, 2013 6:30 PM
  • Thank you for the explanation.

    Thursday, January 31, 2013 6:30 PM