Go gaga over Machine Learning

Daily Testing Tip and Software Testing Club have launched an eBook recently. I’m extremely happy to see the eBook created with one simple but powerful idea which turned into a fabulous eBook for a great cause. The idea was a twitter challenge prompted by Daily Testing Tip 's Anne-Marie Charrett to complete the phrase "If I were a test case I would..." The response was overwhelming to tribute for a cause. The cause is to help Chandrashekar B.N (Chandru). Chandru is a passionate tester and we testers are contributing our sincere prayers and money to beat his Blood Cancer. Yes, Chandru is affected with Acute Lymphoblastic Leukemia. For more information please continue surfing more web links here: http://helpchandru.com | http://bit.ly/9LyGyi | http://bit.ly/cW0u6k .You're helping hands are equally better as you're praying lips. Please help Chandru. Thank you! @xploresqa  is  Shiva Mathivanan : I was patiently going through each sections of eBook page-by-pa...

Well the question does seem easy enough at the first look. This is what the managers across the board have been crying hoarse. Testers need to know business. Or else how can they test? Agreed. But when it comes to performance testers, does this hold good? From a performance testing standpoint, what does a normal performance testers do? In almost all cases, the only way where the critical business flows are identified is via the hits on the web server. If it is a new application, most of the time, the business will have a fair idea of which flows will be critical and those will be handed down to the performance testers. Now our performance tester will come in and write scripts, designs the scenario based on the requirements and executes the test. During the analysis, the following things will be looked at. 1. Server Health 2. Performance issues in code 3. SLAs So keeping this in mind where does the business come in? Does it really matter to the performance tester to understand the ...

My company was using QTP to do the test automation for the past 3-4 years. But we are now moving to cucumber and selenium Webdriver. This blog is about why we are moving away from QTP in my company. One of the main reason that we move from QTP is that it is a reactive approach of writing test automation. The product is finished and the tester starts writing the automation test. Only the tester writes the automation. With cucumber and selenium , writing automation test is a joint effort between the developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. In our case, our QTP automation tester left the company and the QTP vbs code is hard to maintain and to read compared to cucumber and ruby code. I have tried to read QTP code to try to convert the test to cucumber and it is just taking quite a lot of time to just understand wh...

There are a lot of situations wherein we use shortcuts as a workaround while automating. Here are some shortcuts for windows and Microsoft apps:  P.S:  Click on the image and download for quick referencet apps:

Was facing a problem in finding the attributes in an xml file, Here is the code of how to solve that: Const XMLDataFile = "C:\Test.xml" Set xmlDoc = CreateObject("Microsoft.XMLDOM") xmlDoc.Async = False xmlDoc.Load(XMLDataFile) Dim strAttribute Set nodes = xmlDoc.SelectNodes("/Path till the node where the attribute is present") For i = 0  To(nodes.Length -1)       strAttribute= nodes(i).getAttribute("Attribute Name")       MsgBox "Node #" & (i + 1)& ": " & strAttribute Next SampleXml Hope this helps!