Hey just wondering if any of you have been asked to create a suite of smoke tests for a post install check.
Basically the way our app works is when a user logs in, their re-directed to another form where they choose a client. Depending on the users profile they see a bunch of items they can select from a drop down context menu.
I've been asked to create a set of smoke tests, so when a "super user" logs in, it will check to make sure all the possible screens are shown for each client...has anyone done this before because this seems like an odd practice.
I know I can validate if certain objects exists on a form (textboxes, buttons, etc.) but is it possible to check the cosmetics of each form?
Generally it is advisable to keep smoke tests simple and to basic critical functionality so that you can ensure the build is good. It is really a test to ensure that nothing is broken and you can do the subsequent testing.
IMO - to check forms cosmetics seems overboard to me - but if that is what your boss/company needs I guess it can be included but I would not want to return a build for cosmetics.
I completely agree with Lynne. Including cosmetic is certainly overboard. This is not odd practice, I have used it successfully in past and it has worked really well. It saves us a lot of time by rejecting bad build instantly. We had this integrated in our build process itself, so if there is anything broken in the build it will notify everyone.