Hello,
We are attempting to implement Playwright for end-to-end testing in our application. Prior to adding playwright, we are able to run the sample tests included in startup solutions from abp successfully and in non-abp applications we are able to add Playwright per their documentation for Visual Studio and test successfully. However once we add the Playwright into an abp generated solution, then the tests will not complete and seem to get hung up.
I see in the abp docs (https://docs.abp.io/en/abp/latest/Testing), it says that xUnit, NSubstitute, and Shoudly are the libraries already installed for startup projects for testing, but it also says these can be replaced. However, I did not find any resources on how to accomplish this.
Is there any guidance we can get for adding Playwright and having it work with our abp application? Additionally if Playwright is not recommended for end-to-end testing with abp applications, then do you have any recommended ones?
We have a manager that is being called by an appservice in order to do some cross-modules validation checks. If the checks fail, then a BusinessException is thrown. The BusinessExceptions are currently returning Status 403 Forbidden when thrown. Is there a way to make them return Status 400 Bad Request instead?
In our application, we would like to allow users to be created without email addresses as well as allow multiple users to be created with the same email address. Is there any built in way we can accomplish this? If not, what would be the recommended solution to accomplish this?