help in testing tools

[padmaja_obi]

Hi ,
I am padmaja trying to learn testing tools and get job in testing ..so plz any help me in choosing which tool is having demand now and whether to go for automated or manual testing ? and where can i get the related software...i wanted to learn from home only...thanks in advance ..

[zsk_00]

SilkTest and Winrunner are used extensively for testing. This site http://www.aptest.com/resources.html has some stuff on testing tools.

Zafar

[tintin]

I think, QTP has more scope than WinRunner now. SilkTest also has scope, but it's a bit difficult to lear. So my choice is QTP, as it's very easy to learn.

you'll have to request the QTP software from Mercury site. Go through this link: http://download.mercury.com/cgi-bin/...t+Professional

[bharathp]

QTP has more and more scope
learn WinRunner And QTP thoroughly u'll get job soon

[sailaja]

hi this is sailaja
i too wanted to post the same msg as u posted
did u get any replies?
reply bck

[kalyansantosh]

hI
This is Kalyan

All are asking QTP

[crony]

hi padmaja,
Its a good idea to learn testing tools by urself, its better if u learn both manual and automation tools for the interview purpose. But be specific with your resume..and stick on to manual why because you will be having mostly theory only..

And if you stay in hyderabab better go to a testing tools coaching center..
ok all the best..

[syam116]

HI
This is SYAM
First you learn all Testing concepts, then you will get an idea about WHAT IS TESTING and then you go for a Tool (QTP- Easy to learn self with a little bit of real time thinking).
All The Best

[kalyansantosh]

Hi
all are asking QTP But u learn both Manual and QTP u perfect in Manual littlebit of QTP
Im sending Soem Questions





MANUAL QUESTIONS


What is 'Software Quality Assurance'?
1)Software QA involves the entire software development PROCESS
2) monitoring and improving the process,
3) standards and procedures are followed
4) ensuring that problems are found and dealt with. It is oriented to 'prevention'.

What is 'Software Testing'?
Testing involves operation of a system or application under controlled conditions and evaluating the results (e.g., 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'.

Why does software have bugs?
• Miscommunication or no communication
• Software complexity
• Programming errors
• Changing requirements
• time pressures
• egos
• poorly documented code
•
What is Verification?
“Verification” checks whether we are building the right system, and Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.

What is Validation?
“Validation” checks whether we are building the system right. Validation typically involves actual testing and takes place after verifications are completed.

What is a 'walkthrough'?
A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

What's an 'inspection'?
An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader (the author of whatever is being reviewed), and a recorder to take notes.
The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost-effective methods of ensuring quality. Employees who are most skilled at inspections are like the 'eldest brother' in the parable in 'Why is it often hard for management to get serious about quality assurance? Their skill may have low visibility but they are extremely valuable to any software development organization, since bug prevention is far more cost effective than bug detection.

What kinds of testing should be considered?

• Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality.

• White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.

• Unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code, may require developing test driver modules or test harnesses.

• Incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

• Integration testing - testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

• Functional testing – Black box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

• System testing - Black box type testing that is based on overall requirements specifications; covers all combined parts of a system.

• end-to-end testing - similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

• Sanity testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

• regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

• acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
• 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.

• stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

• Performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

• Usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

• Install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes.

• Recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

• Security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.

• Compatability testing - testing how well software performs in a particular hardware/software/operating system/network/etc. environment.

• Exploratory testing - often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.

• Ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.

• User acceptance testing - determining if software is satisfactory to an end-user or customer.

• Comparison testing - comparing software weaknesses and strengths to competing products.

• Alpha testing - testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

• Beta testing - testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

• Mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

What are 4 common problems in the software development process?

• poor requirements
• unrealistic schedule
• inadequate testing .
• Miscommunication

What is software 'quality'?
Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable.

[kalyansantosh]

Hi All


I want Complete Manual Test Notes


Anyone Can Provide me PLZ