ruslan-kurchenko / asserta Goto Github PK

I would define the complete structure of the project.

• Is it sfdx project?
• There will be a lot of classes - should we have them with the namespace as the fflib does it?
• I would also consider an option to have all classes divided but implement a bundler to compile them into one static Assert class. In that case, the library development won't be affected as everyone works on different classes (less merge conflicts) but eventually the lib dist is only one class - Assert

should mocking functionality be a part of this project?
Does it make sense to create a single library with all testing means combined together?
What is the difference between spies mocks, stubs Fakes, dummies?
Mock vs Spy.

• 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.