@ISV Hammer [Pilot] - We have decided NOT to go GA with this product. We will soon be disabling the CLI endpoints and revoke any access. Thank you very much for your valuable feedback during the pilot program.
警告ISV Hammer [Pilot] 已归档。若要重新激活，请联系小组所有人 Vladimir Gerasimov。
How is the Pilot going? This feature could be highly valuable. Do you have any guidance on when it may re-open or enter a beta phase?
As of Winter 21, we are still getting "Your org doesn't have permission to run ISV Hammer." error when trying to run hammer tests against subscriber. Dev Hub is enabled and package namespace is registered in that subscriber org, also it is opted for hammer tests in Setup. Is there any additional configuration required, e.g. opening case in support etc.? Can we get some support re this feature here or is it just dead?
What is the best way to determine why a managed package upgrade hammer test returned a fatal error? We are an ISV and just made our final managed package builds and are testing customer upgrades prior to releasing on the AppExchange. It doesn't get to the Apex tests, so it seems to be during the upgrade process. However any scratch or sandbox org I have tried to manually upgrade outside of Hammer Tests do not have return any errors.
Command:
sfdx force:package:hammertest:run --targetusername XXXXXXXX@xxxxx.com --packageversionids 04tXXXXXXXXX --subscriberfile c:\hammer\CUSTOMER_PROD_orgs.txt --preview --json --apextests -d "2020-07-06 11:45:00"
Here are the results:
=== SubscriberOrgId: 00DEXXXXXXXXXXXXX
=== Status: PACKAGE_HAMMER_FAILED
=== LastModified: Mon Jul 06 22:10:56 GMT 2020
===
=== PackageVersionId: 04XXXXXXXXXXX
=== OrderIndex: 1
=== Conclusion: FATAL
=== Message: Fatal error executing package install/upgrade test.
=== No Package Apex test failures to show.
Thank you,
Justin
1 条评论
@Justin Richmond When we hit a system issue, either while making a copy of the subscriber org or while running the ISV hammer on the copy of the subscriber org, we throw a Fatal Error (mostly the former case). It generates an action item for the ISV Hammer dev team to triage and fix. Since the issue is on the product side, you would not be able to determine why it turned fatal.
I would recommend trying the another run with another subscriber org.
Hello! I was wondering if there was any headway made on running hammer tests after the Winter '20 release? We have also ran into the "ERROR running force:package:hammertest:run: Your org doesn't have permission to run ISV Hammer." It seems to be the same issue others are encountering and would like to move forward with our research into it prior to it's (hopefully) eventual GA release.
We are getting "Your org doesn't have permission to run ISV Hammer." error when trying to run hammer tests against subscriber. Dev Hub is enabled and package namespace is registered in that subscriber org, also it is opted for hammer tests in Setup. Is there any additional configuration required, e.g. opening case in support etc.? This should be already in Beta now in Winter 20, right?
Do you know if the ISV Hammer only supports executing APEX tests? or can ISV Hammer run selenium tests?
We're interested in learning more about this pilot and possibly participating. I opened up a Case in the Partner Portal, but is there a better way to connect with someone about getting involved?