Hey guys n gals,
I am Tanya Cooper, a Computer Science graduate, from AIT, Ma. I worked in 2 of the worlds leading software companies after my graduation, where the last 3 years I spent teaching my colleagues about software testing. I really excelled in teaching with my interactive methods. During this time I realized the absence of proper training material, both for learning as well as preparing for interviews. That is when I decided to compile a periodic list of my Top10 Questions and Answers, which I could post once in every few days.Here is my first top 10 list of Q+A. Hope this provides good knowledge to all those who seek it.
Q1. What is Software Testing?
A1. Software testing is the process used to measure the quality of developed computer software. Testing is a process of technical investigation, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors.
Q2. What is the purpose of Testing?
A2. The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.
Q3. What types of testing do testers perform?
A3. Regression Testing is carried out both manually and through automation. It is mostly done using automation tools, as repeated testing of the same applications is required. It is done to note the changes the application goes through for new functionality, after fixing previous bugs and whether any changes in the design is required. Whenever any change takes place in the Application we should make sure, the previous functionality is still available.
Q4. What is the difference between load testing and intersystem testing?
A4. Inter System Testing: This type of testing is also called end-to-end testing. In this testing, test engineer validates application build co-existence with other software applications.Load Testing: Is also called scalability testing. In this testing, we run the application under customer expected load and customer expected configuration to estimate the load performance
That is, how many users can simultaneously access the application, be it a popular website or a software application.
Q5. How do you do Performance Testing manually?
A5. Performance testing is done to determine the response time for each transaction. So, to do it manually, identify the number of users you want to determine the response time, for a set of actions in the AUT(Application Under Test).
For example, if you want to determine the response for Login, Inbox, Sent Folder and Sign out of an Email application, then provide team of users performing the test manually with the following details:
1. Login Page to Home Page = 2. Home Page to Inbox page =3. Inbox Page to Sent Page =4. Sent Page to Sign out =
Then ask them all to start at the same time and start the stopwatch when they click (when they send request to the server). Now at this point, one should know that they should only start the timer after they enter login credentials and click on "Login" and stop timer only after the response is completely posted on to the browser (status should say "Done" at the bottom of the browser).
These steps should be repeated and start and stop times be noted accurately to arrive at a conclusion.
Q6. What is the difference between load and stress testing?
In Load testing, we actually test the behavior /performance of the software by varying the load on the same from minimum to maximum as specified in the 'Technical Specifications' document.
In Stress Testing, our main intention is to test the software's behavior once it reaches the point where it actually breaks. Here we gradually increase the load while denying more resources (eg. RAM) which are needed to run the same, and test how the application behaves under stressed condition.
Both Load and Stress testing are performed between minimum and maximum specified limits of the application as per the Technical Requirements document.
Q7. What do we analyze in load testing?
A7. We analyze a number of things in load testing, to name a few:1. Response times - Do they appear consistent, is there any degrade over a period of time, or are they higher than what is expected?2. Performance of the hardware components – mid-tier server or the application server, http server, and the database server. The CPU utilization, JVM memory heap of the application server, and the CPU of database server are important for assessing the performance.
Q8. What is the difference between Load testing and Performance Testing?
A8. Performance testing verifies loads, volume and response time as defined by requirements while load testing is testing an application under heavy loads to determine at what point the system response time degrades.
Q9. What are the uses of load testing? What are deferred graphs? And what are the different components in Loadrunner?
Load testing is used to find the minimum and maximum load the application can handle. It ensures the usage of the fixed number of users using the application frequently or concurrently. This exercise is done and ensured using a Load testing tool.
Deferred Graphs give information CPU time usage, Throughput & Response time and the load against the varying number of users.
The components are Generator, Controller & Load Runner Analysis.
Q10. What is the difference between Scalability testing & Load Testing?
A10. Load Testing - Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
Scalability Testing - Scalability testing focuses on the performance of your Web site, hardware and software products, and internal applications at all the stages from minimum to maximum load.
This does not mean that other questions are not important. I compiled this list as per my own reasoning. I am compiling my next list which should be out in a few days.Software Testing Topics on WinRunner, QuickTestPro (QTP), LoadRunner, Manual Testing for Job Interviews
Software Testing: Manual & Automated Testing, WinRunner, LoadRunner, QuickTestPro, SilkTest, TestDirector, Bugs & Error Detection & Reporting
1.12.07
Software-Testing
Software Testing Questions and Answers for Job Interviews consists of topics on Manual and Automated Software Testing, Test Director, WinRunner, QuickTestPro (QTP), LoadRunner, SilkTest, Bug Tracking, Black Box Testing, White Box Testing, Test Cases & Scenarios, Web Testing, & more.
Software Testing Questions & Answers for Job Interviews
Subscribe to:
Post Comments (Atom)
6 comments:
Hey Tanya that was realy helpful.. From where did u get my id?? Plz continue posting and keep me updated for sure!!
Hi,
Thank you very much.. Its really very helpful... try to update me reqularly... Thank you once again...
Hi,
Can you Explain me about Use Case? When & who ewill prepare it? And its template...
RTM? Whats the use of it? who will prepare it? and its template...
Hope you clarify my doubts...
Thanks,
Seethapathi.k
hai tanya i need some questions on qtp as a interviewer what type of questions wil raise.....
seethapathi, you can find post on Traceability matrix at softwaretesting-faq.blogspot.com
thank u Tanya its really help full.....
Post a Comment