Forum Discussion

a_g_reed's avatar
a_g_reed
Occasional Contributor
5 years ago

Newbie Question about Scripting Tests to run across multiple DB

Hi all,   For starters, I'll be frank - I'm a newbie to QA, newbie to automation, and have no tech background. I worked in hospitality for 12+ years and for the past ~3 years have been with a sof...
tristaanogre's avatar
tristaanogre
Esteemed Contributor

Hi, 

 

I used to work for a software company that did POS for amusements and attractions.  So, I've had to answer some of your same questions.  A couple of pointers:

 

1) Don't get caught up in having to have a configuration for each of your clients and run tests for each.  You're not testing their setups, you're testing your software.  So, create scenarios, products, etc., within the software in your testing lab that simulate different possibilities.  Focus most of your attention on the more commmon setups and then, as time allows, start adding in more complicated configurations.  The end result is that you'll be testing all your clients' setups without having to worry about reproducing them.

2) As Wamboo suggests, learn a programming language and start taking advantage of it.

3) When it comes to object identification, again, as Wamboo said, start looking for properties that make an object unique.  It may not be one singular property, but a combination.

 

 

a_g_reed's avatar
a_g_reed
Occasional Contributor
5 years ago

Hi tristaanogre thanks so much for your reply and advice :smileyhappy:

 

I didn't think I'd find someone in the SmartBear Community with POS knowledge so quickly! Believe me, I had no intention of having a configuration for each of our clients lol and was planning on doing as you've suggested - more common setups and adding as we go (great minds think alike). My first real challenge came when I tried to get a script to run across just 2 different QA databases and was faced with this object property conflict. As mentioned in my reply to Wamboo I was able to determine that the TabIndex property seems to be the only unique property from one button to the next (although there will still be differences here from DB to DB so I'm not too sure that's a viable solution for our situation). It looks like I'll be spending some time today and maybe the next few days learning some basics of our programming language. Hopefully, that will clear some things up for me and maybe I'll be able to attack this from a different angle.

 

Thanks again for your time and advice!

 

- Allen