-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OrchardCore Testing #11865
Comments
I haven't used it myself but you may be interested in https://github.com/Lombiq/UI-Testing-Toolbox |
Thanx @rjpowers10 , my point here is to reuse the objects in OrchardCore.Tests and provide a Testing library specific for OrchardCore, so devs can use the same logic - as in OrchardCore source - to test their own modules. |
@MichaelPetrinolis believe it or no I was planned to working on something similar because I'm interesting in Software Testing, It's great to see your input I need to look into your PR soon, If you need help on this I can handle it or at least contribute as much as I can |
@hishamco thanx! Looking forward for your feedback/suggestions. |
Hi @MichaelPetrinolis I'm thinking to organize the testing projects as the following:
BTW we already have a unit tests and some functional tests, I need to dig into Cypress to check if these tests are functional or user acceptance tests or UI For UI tests we already have a test suite from Lombiq that can fit nicely here Our current tests need to be organized in terms of namespaces and group them accoding to the source:
I can work hard in this are if the team agree, the PR that @MichaelPetrinolis is created is a very good start to refactor and move the common thing into a place, so they can be reusable Also we need a set of built-in testing APIs infrastructure, that simplify testsing APIs & modules, instead of repeating the code or do everything from scratch |
Is your feature request related to a problem? Please describe.
When developing an Orchard Core module/app it would be nice to have a Testing Library to get you started with unit and integration testing in OrchardCore terms
Describe the solution you'd like
Create an OrchardCore.Testing library by extracting reusable code from OrchardCore.Tests
The text was updated successfully, but these errors were encountered: