Software Testing and Automation

Purpose of this GUI Testing Checklist is to make sure that GUI of all the applications at <XYZ Organization> are developed and tested according to the known and understood standard. This checklist can give some guidance to the development team as well as QE team. Development team should make sure that during the development they follow guidelines related to the compliance, aesthetics, navigation etc. Onus of testing GUI is on the QE team. Appropriate defect should be raised in the <DTS> system, indicating defect and other relevant information. This GUI test checklist will ensure that all the GUI components are thoroughly tested. This checklist is categorized according to the following sub-sections – Windows compliance standards Validation checklist for tester Field specific test Short-cut keys and hot keys Windows Compliance Standards These compliance standards are followed by almost all the windows based application. Any variance from these standards can result into inconv...

Someone has rightly said that if something can not be measured, it can not be managed or improved. There is huge value in measurement, but you should always make sure that you get some value out of any measurement that you are doing. You should be able to answer the following questions: What is the purpose of this measurement program? What data items you are collecting and how you are reporting it? What is the correlation between the data and conclusion? Value addition: Any measurement program can be divided into two parts. The first part is to collect data, and the second is to prepare metrics/chart and analyses them to get the valuable insight which might help in decision making. Information collected during any measurement program can help in: Finding the relation between data points, Correlating cause and effect, Input of future planning. Normally, any metric program involves certain steps which are repeated over a period of time. It starts with identifying what to measure. After t...

This question was asked by Dina in SQATester yahoo groups. Various reasons were discussed on why software testing is a creative career. This was the original question I'm a senior computer engineering student and I'm really considering testing as a career. I did an internship last summer and as fun as it was, I was disappointed. My question is this: I felt the problem is that the software produced is very much alike and so it turns the testing process to a routine. If you have this, you do that, end of story. I'm not sure if that was related to the whole career or was it just because the project I was working on was like that? Because the main reason I went into the testing career (or looking into it to be exact) is the creativity, not to mention that (I was told) I fit the description. I'd appreciate some guidance :) Greg Ventura Testing is as creative as your company/boss allows it to be. Maybe look for a company that is just getting into serious testing? That way...

Top replies by programmers when their programs don't work: "It works fine on My computer" "Who did you login as?" "It's a feature" "That's weird…" "It's never done that before" "It worked yesterday" "How is that possible?" "It must be a hardware problem." "What did you type in wrong to get it to crash?" "There is something funky in your data" "I haven't touched that module in weeks!" "you must have the wrong version" "It's just some unlucky coincidence." "THIS can not be the source of THAT" "It works, but it's not been tested:" "Somebody must have changed my code." "Did you check for a virus on your system?" "Even though it doesn't work, how does it feel?" "You can't use that version on your system." "Why do you want to do it that way?" "Where were ...

Hope that you have already read first part of this article and familiar with the concept of how web applications are different from traditional client-server applications. If you have not, you might find it useful to read part – 1 as well. In this part we will explore what kind of information is available to the client? What kind of information can be gathered from the pages which client can access? How validation is important to ensure proper security for the web application? What are cookies and how web applications use them? It is very important in web application security testing to gather as much information about your application as you can. You need to find out how people outside your organization will access your web application and what kind of information they can access. Typical information that will be available to any person outside your organization could be categorized as Comments & Sensitive information embedded in the HTML source code Error messages generated at th...

Web application and Client-Server, are they same? This question is very common in software testing interviews, if you are part of some e-groups related to testing, you might have heard it many times from different people. There are numerous differences in Client-Server and Web application architecture. As a tester if you are testing Web applications, it is important to understand what Client-Server architecture is and how Web is different from traditional Client-Server architecture. Web is a specialized version of client server network, but it has got noticeable differences. In client server network, computing resources are conserved by delegating complex and time consuming task to powerful, expensive computers called server. These server machines are much more powerful in terms of large storage and computing power. They do all the computing and delivers result back to the machines called client over a communication path. Thus client-server architecture comprises of server, client and ...