Robustness Testing - Qa Faqs
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Robustness Testing - Qa Faqs as PDF for free.
More details
- Words: 374
- Pages: 3
Cookie Monster
COOKIE MONSTER SYSTEM ROBUSTNESS - QA FAQS Date 07/10/07
Version 1
Description Initial document
Impetus Confidential
Author
Page 1 of 3
Cookie Monster
•
Application storing Web log in Log Server disk (Web Log Server and Log Sever Handshaking).
1. Check to see if multiple instance of an application can be run simultaneously. 2. Ensure program recovery from abrupt shutdown (killing the copying process). 3. Mechanism to verify that lost network connections are detected handled and appropriately reported (link down problem). 4. How system is handling the remote file errors (file not found /files are corrupt/ server down) 5. Not enough space in the log server. •
Testing Web Log Parser
1. Check to see what happens when you start a Web Log Parser process that is already running. 2. When program “kill” then see if program can be restarted. Ensure that program recover from old state. 3. How system will behave when Web Log data missing file error. 4. How system will handle invalid file (corrupt file) /invalid data (corrupt data). 5. How application will be working in low memory (RAM/Disk space). •
Testing Log Aggregator (Handshaking of Log Aggregator with Web Log Parser).
1. Check to see what happens when you start a Web Log Parser process when Log Aggregator is already running. 2. When program “kill” then see if program can be restarted. Ensure that program recover from old state. 3. How system will behave if input data file is missing. 4. How system will behave for invalid file/data. 5. How application will be working in low memory (RAM/Disk space). •
Testing Scoring System
1. What happens when you try to run an application that is already running. 2. Ensure program recovery from abrupt shutdown (killing the copying process). 3. Mechanism to verify that lost network connections are detected handled and appropriately reported. Verify that the connection is properly re-establish when the cable is restored, that the re-connection is appropriately reported, and the application continue execution as appropriate . 4. Network Link/Port unavailable. Impetus Confidential
Page 2 of 3
Cookie Monster
5. How system handling Input File not found error. 6. How system handling Corrupt data. 7. How system handling low memory problems.
Impetus Confidential
Page 3 of 3
COOKIE MONSTER SYSTEM ROBUSTNESS - QA FAQS Date 07/10/07
Version 1
Description Initial document
Impetus Confidential
Author
Page 1 of 3
Cookie Monster
•
Application storing Web log in Log Server disk (Web Log Server and Log Sever Handshaking).
1. Check to see if multiple instance of an application can be run simultaneously. 2. Ensure program recovery from abrupt shutdown (killing the copying process). 3. Mechanism to verify that lost network connections are detected handled and appropriately reported (link down problem). 4. How system is handling the remote file errors (file not found /files are corrupt/ server down) 5. Not enough space in the log server. •
Testing Web Log Parser
1. Check to see what happens when you start a Web Log Parser process that is already running. 2. When program “kill” then see if program can be restarted. Ensure that program recover from old state. 3. How system will behave when Web Log data missing file error. 4. How system will handle invalid file (corrupt file) /invalid data (corrupt data). 5. How application will be working in low memory (RAM/Disk space). •
Testing Log Aggregator (Handshaking of Log Aggregator with Web Log Parser).
1. Check to see what happens when you start a Web Log Parser process when Log Aggregator is already running. 2. When program “kill” then see if program can be restarted. Ensure that program recover from old state. 3. How system will behave if input data file is missing. 4. How system will behave for invalid file/data. 5. How application will be working in low memory (RAM/Disk space). •
Testing Scoring System
1. What happens when you try to run an application that is already running. 2. Ensure program recovery from abrupt shutdown (killing the copying process). 3. Mechanism to verify that lost network connections are detected handled and appropriately reported. Verify that the connection is properly re-establish when the cable is restored, that the re-connection is appropriately reported, and the application continue execution as appropriate . 4. Network Link/Port unavailable. Impetus Confidential
Page 2 of 3
Cookie Monster
5. How system handling Input File not found error. 6. How system handling Corrupt data. 7. How system handling low memory problems.
Impetus Confidential
Page 3 of 3
Related Documents
Robustness Testing - Qa Faqs
October 2019 14
Testing Faqs
November 2019 14
Testing Qa
November 2019 14
Testing Faqs
October 2019 9
Manual Testing Faqs
October 2019 8