Replies: 1 comment
-
|
Regarding your first error in B2CAUthTokenHelper_Test Class the testGetB2CAuthTokenByClientIDValueSuccess... We had similar issues due to the user executing tests not having the permissionsetgroup assignment giving them the correct access to manipulate the B2C_Client_ID__c. The test wasn't failing on the INSERT for some reason, but it also wasn't getting the necessary ID to do the lookup within the Start/Stop test block. We had to alter the test to build a user with the assignment and then Run As that user... That seems like something that should be part of the code base. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We succesfully deployed the connector to a sandbox.
But as we wanted to go on deploying to other testing instances we noticed there are a lot of errors coming in.
I'm expecting that some are subsequently, but they need to be fixed anyway.
In B2CAUthTokenHelper_Test Class the testGetB2CAuthTokenByClientIDValueSuccess fails with the error message "System.AssertException: Assertion Failed: Expected a valid authToken to be returned".
Also the Class QueryTest multiple times e.g. the method groupByTest with the message:
"System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, AccountTrigger: execution of AfterUpdate
caused by: System.NullPointerException: Attempt to de-reference a null object
Class.Account_Handler.afterUpdate: line 107, column 1
Class.TriggerHandler.run: line 68, column 1
Trigger.AccountTrigger: line 8, column 1: []"
Does somebody has the same issues when running the tests or better, can anybody help?
These errors need to be fixed otherwise I can't deploy to production instance.
Beta Was this translation helpful? Give feedback.
All reactions