qastreet.com
what is Testing :
Intentionally finding errors from the software is called testing. Errors may be functional errors or usabulity errors or excess functonality which is not defined by client.
Inadequately Tested software negetive impacts:
It is difficult to test software products, as evidenced by the problems we find in our software every day. The customer risks of not adequately testing software can be as minor as user inconvenience or as major as loss of life. Not only are there customer (end-user) risks for inadequately tested software, there are also corporate risks. Especially for mature products, an inadequately tested product can have serious negative consequences for a company.
So, What an organizations doing now :
Organizations are actively working to improve their testing processes and increase the number of people devoted to product test.However, many organizations still rely on structured manual tests that test the product at its uppermost levels, the levels closest to the user. If you need to reduce the number of defects or meet stringent performance or reliability criteria, then user level testing is not adequate. You must look at the product architecture and develop tests based on the major modules, the interactions between those modules, and the flow of data between modules
Every Test consists of 3 steps :-
¨Planning : Inputs to be given, results to be obtained and the process to proceed is to planned.
¨Execution : preparing test environment, Completing the test, and determining test results.
¨Evaluation : compare the actual test outcome with what the correct outcome should have been.
Every project need a tester :
Which projects may not need independent test staff? The answer depends on the size and context of the project, the risks, the development methodology, the skill and experience of the developers, and other factors. For instance, if the project is a short-term, small, low risk project, with highly experienced programmers utilizing thorough unit testing or test-first development, then test engineers may not be required for the project to succeed.
What are Test Deliverables :
Test Plan, Test Case, Defect-Fault, and Status Report are the sets of test deliverables in any testing phase. This does not represent a definitive set of test deliverables but it will help any test organization begin the process of determining an appropriate set of deliverables. Test deliverables’ goal is to capture the required content in a useful and consistent framework as concisely as possible
How the testing is performing:
Intentinally breaking the software to find errors, chek wheather software is userfriendly or not, check as per the client requirements wheather this software is created or not, check wheather this software work for long hours or not (heavy load).
Why the above things are done :
To find, if it has happen in real time , then how the software is reacts,how the end-user feels working with our software.
What is the goal of Software Testing :
Ultimate goal is Quality in software product in terms of functinality, user friendly.
What is the out put of testing :
Satisfied Customer and quality software
When the testing Activites are Started :
the client approches software company to create a product , if deal is over then Testing activities are start..
Where Testing is Performing :
it may be client place(on-site) or in our company . Some time you should go to the clinet place and perform testing on client place , this know as onsite testing.
How many types of Testing Teams are there :
1.General Testing Team : Development people and testing people from the same company
2.Thrird Party Testing Team : Development is doing by some other company,and they assign testing to another compnay.
Who will form Test Team and when :
Project Manager and QA Manager will from test team, when the specification documents are created.
How Many Testers required for a project :
That depends on the project
Is there any ratio between developper and tester :
No ratio compinies maintaining.
who will involve in this Entire Cycle:
Tester, TestLead, QA Manager, Project Manager, Developper, Client.
Some of Terminologies using in Testing :
Software specifications,functional specification,Test Plan, Test Cases, Test Scenarios,Bug Report,Modification Request,Quality Assurance,Test Buiilds, Test Data, Ead value calculator,revivews,Inspections,....
When can Testing be stopped :
Its difficult to determine exactly when to stop Testing.The following are some of the cases which can help to decide when to reduce/stop Testing:
1)Deadlines(Release/Test Deadlines etc)
2)Test cases completed with certain percentage passed.
3)Test budget depleted.
4)Coverage of code/functionality requirements reaches a specified point.
5)Bug rate falls below a certain level.
6)Beta or Alpha testing period ends.
Friday, March 5, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment