Skip to main content

#Regression0 discussing

Which tool is best for Salesforce test automation?

ACCELQ

Provar

Copado

Tosca

Cypress

TypeScript

Test Sigma

Share your comments on the tools.! what works best for custom LWC components and skuid pages?

#Salesforce #TestAutomation #Regression #API #Lighting UI #Automated Testing #Automation

3 answers
0/9000

We've discovered a #Regression in the behavior of Crypto.generateDigest() in #Winter19.

 

To reproduce this, run tests against the following two Apex Classes, the first on API version 43 and the second on API version 44. We'd expect that a change in the exception message to be part of the API contract, so the fact that version 43 no longer behaves as it used to seems like a #BUG:

 

@isTest

public class CryptoGenerateDigest43_Test {

    @isTest

    public static void test() {

        try {

            Crypto.generateDigest('INVALID', Blob.valueOf(''));

        } catch (System.SecurityException e) {

            System.assertEquals('INVALID MessageDigest not available', e.getMessage());

        }

    }

}

 

@isTest

public class CryptoGenerateDigest44_Test {

    @isTest

    public static void test() {

        try {

            Crypto.generateDigest('INVALID', Blob.valueOf(''));

        } catch (System.SecurityException e) {

            System.assertEquals('no such algorithm: INVALID for provider SC', e.getMessage());

        }

    }

}

 

It looks like the underlying implementation of Crypto.generateDigest() delegates to the Java backend, but the java.security.NoSuchAlgorithmException message is now propagated directly even in older API versions.

 

We've filed this issue with support as case ID 5000M00000mQPatQAG

0/9000

Also, maybe a bug, for some reason my custom metadata records aren't being pushed/pulled. I've just tried this in a brand new dx org, and the object is being pulled, but any records created aren't pulled, and manually created records aren't pushed. Is this per chance a regression?

2 comments
0/9000