I am working on an existing test automation framework that uses the following for UI tests on a windows application:-
- C# for creating UI cases
- winAppDriver to interact with UI objects
- nUnit for validation
- specflow for BDD
I don't have much idea about microsoft projects. Here is a simple structure of the project:-
- Application
- Source
- Modules
- features
- Tests
- features
- Modules
- Source
Each test folder has a "app.config" file in it that supplies the config for the test to work like DB username, pwd, services urls etc.
We execute our test case from "Test Explorer" pane in VS Enterprise which is not the best way if the test cases need to be run remotely in jenkins. As I said I don't have much frame of reference when it comes to Microsoft apps. So, here are some questions to which I have been looking for answers; there seems to be no definite consensus online. Just curious to know how others are maintaining their projects. Here goes:-
- is there a jenkins friendly way of running these test cases? using a cmd line or a runner file perhaps?
- if I find a way to accomplish #1 how do I inject app.config properties at runtime?
- how does one execute these cases on remote machine? Mine is a desktop windows app. What would a high-level strategy look like? I assume I will have to get a remote machine and install the app on that machine?
any pointers, resources to read about would be helpful. Just looking for a nudge in the right direction.