Hopefully the functionnalities of the application itself and the installer are unrelated, and you can test them in any order.
Edit: Answer to comment Let me reformulate : hopefully the two assumptions :
1) My installer will put my user system in the proper state for my application to run
and
2) Provided the system is in the proper state, my application runs properly
are unrelated. Obviously, if your installer fails, your application won't work if installed by the installer :)
If you have doubts about that (and in particular are unsure about the definition of "proper state") that's probably the first thing you should test : what kind of "state" do you need for your application to run. Then you can test the installer and the application independantly
manpreet![Tuteehub forum best answer]()
Best Answer
2 years ago
I developed one application, and starting the testing phase soon,
While I'm trying to setup a testing plan, I have one question!
Shall I start by testing the actual application functionality, or the installation procedure first? (Please note that the installer is an actual project we have)
Thanks,