give me difference between the strategy and appraoach in the software testing?
357145
An approach is more tectical... it tells you how you will test the software. A strategy is more high level approach and less detailed.
772597
The software you are using is the key.  What are you using?
631778
It would be best if you could further elobrate the question. \nIf u r saying about "software testing" then refer following:\n1, dry run the software with test table\n2, unit testing of its individual component\n3, run same feature with different configurations (change user role , environment etc)\n4, run any testing software against it!\netc\n\nelse if u r saying about "exam-test" then refer following:\n1, List the prime numbers\n2, use array as stack\n3, find factorial\netc
86290
Use on of the following.\n1. Symantec Java Cafe\n2. Microsoft J++\n3. Microsoft J#
329830
In software development, testing is usually required before release to the general public. This phase of development is known as the alpha phase. Testing during this phase is known as alpha testing.\n\nIn the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques. This is usually done by a dedicated testing team. This is often known as the second stage of alpha testing.\n\nOnce the alpha phase is complete, development enters the beta phase. Versions of the software, known as beta-versions, are released to a limited audience outside of the company. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta-versions are made available to the open public to increase the feedback field to a maximal number of future users.\n\nTesting during the beta phase, informally called 'beta testing, is generally constrained to black box techniques although a core of test engineers are likely to continue with white box testing in parallel to the beta tests. Thus the term beta test can refer to the stage of the software—closer to release than being "in alpha"—or it can refer to the particular group and process being done at that stage. So a tester might be continuing to work in white box testing while the software is "in beta" (a stage) but he or she would then not be part of "the beta test" (group/activity).\n\nIn a corporate environment, an Alpha test is not implemented in the workplace, but done in labs and simulated settings.  A Beta test is implemented in a live environment, but the applications that the software would replace are run as well so that in case the software being tested fails the operation can continue.
590336
http://dhvrm.blogspot.com/2006/04/what-is-beta-testing.html
722181
What I usually do is surf a book site like amazon, barnes & noble, chapters and when I find a book that appears to be what I want, I then do a search on a file sharing network for an ebook version of it.\n\nI know it is not the most legal way of doing it, but for personal use I think it would be ok. \n\nJust so you know, from one programmer to another, I have found very few books dedicated strictly to testing. You are better off looking at general "programming design and good practices" types of books which will also have several chapters dedicated to good testing... both system and unit testing if it is a really good book.
449549
its a program under test, meaning its done yet feed back is needed for the development of that program :)
747389
It should be 'course of action'.\nHow about 'format'? Or 'method'?
317798
http://www.paroxys.com/SoftwareRiskManagement/SoftwareRiskManagement.htm\n\n\nscroll down.. these is an explanation and a diagram.\n\nHope it helps.\ni want my 10 points if it helps ya :)\n\nThe classic software development triangle states that projects must balance time, quality, and features against each other. When SAP projects slip, enterprises often first try to buy more time by throwing more people at the testing problem and having them work overtime on nights and weekends in order to maintain quality and features. But without the right tools, people and processes, this attempt fails, and quality suffers resulting in threats to business continuity
515606
The Beta version is being tested (it's called Beta testing, for obvious reasons). There are many different kinds of tests you can and should run during development, but before you can issue your final release, you need to submit your application to a group of people (Beta testers) who will be doing the same kinds of things with your program as the end users. In most cases, beta testers are actual end users who want to get a preview of the application (Beta releases are almost always free). The idea is that these users will report any bugs that they encounter, giving the developers a chance to fix them before releasing the final "stable" version.
1121549
A preliminary version sent out into the world to see if there are any bugs in it. If you have problems, report them immediately. Another test, though unorthodox, is to let a toddler play with it. Toddlers always find ways to crash software, be it pounding the keyboard or attacking the mouse.
1113013
ABOUT SOFTWARE TESTING?
906324
An option strategy is usually implemented by combining one or more option positions and zero or more underlying positions. The option positions used can be long and/or short positions in calls and/or puts at various strikes.\n\nGenerally, options trading strategies can classified to be bullish, bearish or neutral. In the case of neutral strategies, they can be further classified into those that are bullish on volatility and those that are bearish on volatility.\n\nAnd That's My Best Option Answer!
699428
The use cases should involve all the logic associated with the system.  From your description, it sounds like the use cases should be:\n*Recommend Policy A [with associated age, occupation, location logic to warrant this choice]\n*Recommend Policy B [same]\n. \n. \n*Recommend Policy N [all of which have a recursive loop to potentially recommend additional policies and logic regarding when to exit the loop, say after 3 policies are recommended]\n*Do not recommend a policy\n\nOr you could have just two use cases - Recommend policy or policies, and Do not recommend a policy.\n\nIt depends on how detailed (and how many) use cases you want.\n\nIt doesn't sound like the actual selling and application process is part of the system, since the "staff" sells it to them and not the computer system.\n\nYou may also have use cases for entering and exiting the system, and for verification of a user's identity.  These are standard for any computer system, but obviously would not be the main focus of your answer.  Perhaps they are "assumed," but you should probably devote a sentence or two to them anyway.
514671
These may help:\n\nhttp://www.google.co.uk/search?hl=en&q=types+of+software+testing&btnG=Google+Search&meta=
91151
Telling the people writing the program exactly what you want the software to do.  NOT HOW to do it, just WHAT to do.  This should be agreed upon before the code-writing begins.  Otherwise you find yourself having to re-write lotsa code to do what the customer actually wants it to do.