Port the Java AssertJ library

[ruslan-kurchenko]

• Will we use AsserJ as a base of the asserta?
• Any other alternatives?
• If any, we need to define a list of items (Assert Types) with priorities to implement: Strings, Objects, Lists, Maps, Sets, sObjects, etc.

[Nara7788]

If any, we need to define a list of items (Assert Types) with priorities to implement: Strings, Objects, Lists, Maps, Sets, sObjects, etc.

How about such a list. The higher the list, the higher the priority.

• Apex primitives (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_primitives.htm)
• Apex Collecitons (List, Set, Map)
• sObject
• class
• interface
• enum
• other apex namespaces (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_reference.htm)

[Nara7788]

Will we use AsserJ as a base of the asserta?
Any other alternatives?

How do you think it will be easier and more correct?

1. Do porting AssertJ
2. Borrow API and implement it as we want and as the language allows us.

[ruslan-kurchenko]

@Nara7788 Yes, I like the prioritization list.

And about AssertJ - I would start from scratch by inheriting the API. AssertJ is quite complex inside to be able to port classes from Java to Apex. Plus, Apex much more limited than Java and we will need to work without Generics.