何时致电支持? 2次测试失败...... [英] When to call Support? 2 tests failing...

查看:45
本文介绍了何时致电支持? 2次测试失败......的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,我们在新的HCK for Windows 8硬件测试中学习绳索时遇到了很多麻烦。我们正在设法为Windows 7及更早版本定期测试和提交产品,但即使这个新套件看起来更简单,但是很难将所有信息整合在一起。我希望有人可以给我一些建议。



我们有一些外围设备在Web86 BasicPerf base(Manual)和Webcam UsageIndicator base的x86和x64测试中一直都失败了(手册)。所有较长,详细的测试都在通过,这些是无人驾驶的UVC产品,所以我们可以尝试的限制为
。第一个似乎是一个延迟问题(可能是由于我正在试验的低于标准的测试设置)。第二次测试的失败对我来说不那么有意义;从日志看起来好像测试过早中止而不是
而不是因为它执行的状态检查失败,没有任何有用的错误我可以使用。这很难调试,因为每次运行测试时,失败似乎都发生在不同的时间(可能会有一个随机序列,以防止
通过手动确认步骤作弊)。 



此时我确信产品应该可以接受完整的硬件标识,这只是破解最后两个测试的问题。我应该在支持下拨打电话吗?我学习新HCK的最大敌人是我所需要的信息似乎是如何传播并拼凑在一起的,这也是支持的情况。拨打电话的费用高达199英镑,但我不明白打电话是否会真正解决问题或涉及的问题。我不希望为每个问题支付199英镑来赚取
只发现支持非常有限 - 是否有人能够就他们的经历提出建议或指出我对该流程的完整解释?如果199英镑将意味着我解决了这两个问题并帮助所有
方式获得徽标,那么它绝对物有所值。



顺便提一下我正在测试的模型甚至没有物理上的使用指示灯,但收集器仍然根据需要选择测试。自述文件的解释是否足以豁免提交,理由是实际的
设计显而易见,或者它是否仍需要通过支持电话预先批准?



抱歉,我很困惑。

Hello, we've been having a lot of trouble learning the ropes on the new HCK for Windows 8 hardware testing. We were managing to get products tested and submitted regularly for Windows 7 and earlier, but even though this new suite is much simpler-looking it's proving difficult to pull all of the information together. I hope someone can give me some advice.

We have some peripherals which are consistently failing on x86 and x64 tests for Webcam BasicPerf base (Manual) and Webcam UsageIndicator base (Manual). All of the longer, detailed tests are passing, and these are driverless UVC products so there's a limit to what we can try. The first seems to be a latency issue (possibly caused by a sub-par testing setup, which I'm experimenting with). The second test's failures make less sense to me; from the logs it looks as though the test is aborting prematurely rather than as a result of a fail in the status check it performs, with no helpful errors I can work with. It's hard to debug because the failure seems to occur at different times each time I run the test (presumably there's a random sequence to this one to prevent cheating with the manual confirmation steps). 

At this point I'm certain that the products should be acceptable for a full hardware logo and it's just a matter of cracking these last two tests. Should I be raising a call with support? My biggest enemy in learning the new HCK has been how the information I need seems to be spread around and pieced together, and this is the case with support too. It's pricey at £199 for a call yet I don't understand whether making the call will actually solve the problems or what's involved. I don't want to potentially be made to pay £199 per problem only to discover that the support will be very limited - is anyone able to advise on their experiences or point me towards a full explanation of the process? If the £199 will mean I get walked through both problems and helped all the way to a logo then it's definitely worth the money.

Incidentally one of the models I'm testing doesn't even physically have a usage indicator light but the gatherer still picks the test up as required. Will a readme explanation be enough to exempt that submission on the grounds that it's obvious from the physical design, or does it still have to be pre-approved with a support call?

Sorry, I'm so confused.

推荐答案

请复制/粘贴此主题的错误日志。

Please copy/paste the error logs on this topic.

确保您已下载并安装了适用于HCK版本的最新过滤器。

Make sure you've downloaded and installed the latest filters for your HCK version.


这篇关于何时致电支持? 2次测试失败......的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆