Currently I am testing a desktop application on which I need to double click on a batch file and login screen gets open along with a cmd.exe screen.
Can any body tell me the best testing approach to test this type of application. Also right now multiple instances can be opened by double clicking on the batch file and login with the same user credentials ? Is is correct or instance of desktop application can be opened single as per the best practice ??
Is there a way to avoid the desktop interaction all together.
Most scripting language will have a way to call the command line. It would be far easier to write a script that calls the command line, pipe the output into a variable, then just verify the output using regular expressions or simple substring searches.
This way you can run many tests in parallel and not have any cross contamination of results.
Also right now multiple instances can be opened by double clicking on the batch file and login with the same user credentials ? Is is correct or instance of desktop application can be opened single as per the best practice ??-Akram
This completely depends on end users. If they are using multiple instances it is ok.
Not sure the specific you've mentioned may designate the approaches to test the application. All the regular test practices are applicable here. If you mean the automation, I would say that strongly depends on the framework the application's UI is built over. Regarding the several instances it's case-by-case matter. However if you allow the application to run several instances consider the concurrent access to the files and other resources
You have to check with your busniess analyst if several instances are allowed, if so how many instances are allowed/ how many instances a user can login at a time. it always depends on your businees requirements.