-
Notifications
You must be signed in to change notification settings - Fork 3
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
Steps to test the repo functionalities (OSOE-803) #110
Comments
There are tests, see all the |
So you rely heavily on the UI tests. I assume there's a web host that anyone can try out the features without touching the tests. IMHO the tests could only used for testing use cases |
I don't really understand. The tests are indeed for testing :). Isn't this what your issue is about? If you mean documentation about how to use these features, I believe we have that. Is there anything specifically that you're missing? |
I made it unclear on the title, what I need to do is check the features without touching the UI tests. I presume this is a normal flow, or are you using TDD? |
One more thing how can I run the UI tests from within the repo? is there any integration to VS Testing Tools or I should use CLI instead? |
What do you mean by "check"? I really don't understand what you're looking for, sorry. If you want to try out the features, just add the NuGet packages to a standard OC app. You need a solution for the tests, for which I recommend https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions. |
It would be nice if you added steps to test the various features in this repo
Jira issue
The text was updated successfully, but these errors were encountered: