TestersBlog

I was undergoing training in Edista Testing Institute. We were testing a calculator (not the Microsoft one) and were making comparisons to Microsoft calculator.

I wanted to  do some automation testing and searched automation tool – AutoIT. It allowed me to automate some tests but needed lots of test inputs.

As a co-incident I was introduced to Testers Desk and that was a hope for me. This post speaks about test automation which I did on Microsoft Calculator with the help of www.testersdesk.com

I used Quantified String Generator Output and feeded that as num1 and num2 in N-way/Random Test Case Generator to generate a list of random numbers that I can feed in to test the calculator.

Example:

num1:2,4,6,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59,62,65,68,71,74,77,80,83,86,89,92,95,98,10
operator:+,-,*,/
num2:2,4,6,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59,62,65,68,71,74,77,80,83,86,89,92,95,98,10

I got 4900 combinations I could run my script on. I got this output and it was so nice to see 4900 combinatons.

Continues till 4900th combination

Take a look at my script that I ran in AutoIT and I even found bugs with it on Microsoft Calc:

Send(”#r”)
WinWaitActive(”Run”)
Send(”calc.exe{Enter}”)
WiNWaitActive(”Calculator”)
Send(”5{/}0{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”#r”)
WinWaitActive(”Run”)
Send(”notepad.exe {Enter}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)

Send(”!{TAB}”)
Send(”87{/}54{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”2{/}61{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”87{/}87{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”7{/}82{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”69{/}6{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”41{/}12{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”34{/}81{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)
WinWaitActive(”Untitled -”)
Send(”^v{Enter}”)
Send(”!{TAB}”)
Send(”95{/}14{=}”)
Send(“{ESC}”)
Send(”^c”)
Send(”!{TAB}”)

I used the output file I generated to compare results with the calculator we were testing.

I recommend newbie/experienced testers to make use of TestersDesk.com to fasten their work of thinking about test inputs. Its free.

Combine it with any other test automation tool for test automation else use it in your manual testing.

Stop waiting and start Testersdesking.

What people mean to say when they say “Bad Software”? Different people think different things about “Bad Software”. It can be termed in different contexts.

A software might not perform as claimed, it might fail, it might not perform the operations properly or many other factors that come into picture.

How does a Software become Bad Software? Who are the contributors to the Bad Software? Why the Software becomes a bad software inspite of being tested? What consequences should the customers need to face because of a bad software? What risk is posed by these consequences? Are the companies aware of these things?

I am not sure but I think this is all because of “Scripted Testing” or “Automated Tests”. Scripted testing might miss some of the problems which could be found out by manual testing. Scripted Testing might find some problems but the rate at which the problems can be found by scripted testing is less than the manual testing.

I don’t mean that “Automated Tests” are not good but while a tester does “Automated Tests” he/she should concentrate on even the “Manual Testing”.