Test Environment :Environment that is to be created for the testing team to execute the tests manually as well as by automation.This test environment is the integration of software,hardware,...
Dear Friends,Tes Environment : It is nothing but Software, Hardware components to execute our tests smoothly.DB installing is nothing but installing DB on server/System.Configuring here refers to givi...
What are the quantitative metrics collected in testing projects?
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Nov 18th, 2009
A Test metric is a standard means of measuring some attribute of the software testing process. They establish test progress against the test schedule and may be an indicator of future results. Metrics are produced in two forms – base and derived metrics.
Examples of base metrics:
# New test cases
# Regression test cases
# Test cases run
# Test cases not run
# Passes
# Fails
# Test cases under investigation
# Test cases blocked
Examples of derived metrics:
% Test cases complete
% Test cases passed
% Test cases failed
% Test cases blocked
% Test defects corrected
HiMetrics can be prepared at any level of SDLCRequirements:-> Schedule Variance-> Effort Variance-> Frequency of CR's, etcTesting:-> Test cases count per module-> Test cases types: ...
A Test metric is a standard means of measuring some attribute of the software testing process. They establish test progress against the test schedule and may be an indicator of future results.&n...
Suppose a db has just been upgraded from Oracle 10g to 11. What testing factors will you look at?
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Nov 29th, 2009
1) Test the upgrade itself. Do problems arise? Has anything new been introduced that needs to be accounted for? If so, make sure it works properly.
2) Run functional tests that rely on the database to ensure they function properly.
3) Run performance tests to ensure data is obtained within specified performance parameters.
4) Ensure data integrity is maintained after upgrade. Contstraints, for example, should still be handled as expected.
5) Run load and/or stress test to ensure the upgraded database still handles user load and performs well under the most business-critical resource-intensive circumstances.
6) Test the Oracle client. Ideally, any issues will have been caught in the upgrade test, but it is a necessary step in the process.
1. Identify and execute the testcases which can exercise all the database operations from application.
2. Execute automation scripts
3. Execute performance tests
4. Identify and execute testcases which update the existing records to test the backward compatibilty.
1) Test the upgrade itself. Do problems arise? Has anything new been introduced that needs to be accounted for? If so, make sure it works properly. 2) Run functional tests ...
Checklist for recovery testing
What is recovery testing? In what ways we can do it? List the checklist for recovery testing.
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Jan 1st, 2010
Recovery testing is the forced failure of an application to determine whether it can recover without impaired functionality or data loss. The breadth and depth of recovery testing depends on the mission-critical nature of the application.
Some examples are:
1) Take a database down while an application is sending transactions and then bring the database back up again. Verify there is no loss of data and that the application resumes in a way that users will know how to proceed.
2) While an application is running, restart the computer and validate there is no data loss and that users can proceed without negative side effects.
3) While application is receiving data over a network, unplug and reinsert the network cable to validate the application's ability to continue receiving without loss of data.
4) Restart the computer while a browser has a number of sessions running simultaneously and then determine if the browser is able to recover all of them.
Recovery testing is the forced failure of an application to determine whether it can recover without impaired functionality or data loss. The breadth and depth of recovery testing depends on the missi...
When you ask users to test software, what approach should they take?A. They should scan the user manual looking for situations of interest which they then test, menu option by menu option.B. They sit at the terminal, dreaming up situations randomly visiting all the features of the system to ensure they...
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Nov 13th, 2009
The only reasonable answer is D) Users cannot test software effectively.
Users typically test a system during the Beta release of a product. Though companies should not rely only on this type of testing, it is useful in uncovering defects at little cost to the company. Throughout this period, users perform their day-to-day activities and are not thinking about product quality. They rarely if ever scan the user manual looking for situations of interest to test, so the answer is not A). They generally don't dream up situations randomly to visit all of the features of the system, so the answer is also not B). They don't have access to the company's business processes, so the answer is not C).
I still cannot understand why people are willing to waste time in posting already answered questions? Can you please use the search feature in this site and save everyone's time including yours? This does really anger a lot of people FYI
HI
Ans D is correct
They will not have any idea of testing the software
CNU
Faults found by users in production are due toa. Poor quality softwareb. Poor software and poor testingc. Bad luckd. Insufficient time for testing
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Nov 13th, 2009
Faults found by users in production are due to:
The best answer is B) poor software and poor testing
A) is true, but not as complete as B)
D) may also be true, but not as complete as B)
E) is obviously false because quality has nothing to do with luck
HI
I feel it's due to poor quality, here the issue may come due to poor sw, but finding the issues is the major responcibility of a tester than dev team, but there that option was not there, so i can to the option B is correct, poor software and poor testing
CNU
Faults found by users in production are due to:
The best answer is B) poor software and poor testing
A) is true, but not as complete as B)
D) may also be true, but not as complete as B)
E) is obviously false because quality has nothing to do with luck
In what scenario concurrency testing is done? Give real time scenario for the same.
Answered by: kurtz182
View all questions by kurtz182 View all answers by kurtz182
Member Since Nov-2009 | Answered On : Nov 6th, 2009
Concurrency testing is performed when there are two or more scenarios being tested on the same application at the same time. A common form of concurrency testing takes place when two users are logged into the same application and a tester wishes to determine how their activities impact one another. It is commonly employed to test web sessions and state management.
HI
This will be comes under Multi user testing, ie testing the application by more than one user at same time...
The intention is find the behaviour of application when it was using by more than one user, ie to verify the speed, performance, how data base is responding, etc
CNU
Concurrency testing is performed when there are two or more scenarios being tested on the same application at the same time. A common form of concurrency testing takes place when two users are l...
hi!~see the metric represents measurement of software attributes.. the most attributes of a software can be its length ..i.e nos of coding lines..test defect density= no of defects/no of coding linesi...