what is software testing?
454150
going through all the possible options in a program, and even some of the impossible ones, to see if there are any bugs in it
1175942
http://www.stellman-greene.com/aspm/content/view/39/41/\n\nfurther....\n\nCem Kaner, co-author of Testing Computer Software has suggested that test plans are written for two very different purposes. Sometimes the test plan is a product; sometimes it's a tool. It's too easy, but also too expensive, to confuse these goals.\n\nIn software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including\n\nScope of testing \nSchedule \nTest Deliverables \nRelease Criteria \nRisks and Contingencies \n\n#Test plan template, IEEE 829 format\n\n------Outline\nTest Plan Identifier \nReferences \nIntroduction \nTest Items \nSoftware Risk Issues \nFeatures to be Tested \nFeatures not to be Tested \nApproach \nItem Pass/Fail Criteria \nSuspension Criteria and Resumption Requirements \nTest Deliverables \nRemaining Test Tasks \nEnvironmental Needs \nStaffing and Training Needs \nResponsibilities \nSchedule \nPlanning Risks and Contingencies \nApprovals \nGlossary \n\n###Test plan identifier\nThe test plan identifier number is.......( to identify this test plan, its level and the level of software that it is related to. Preferably the test plan level will be the same as the related software level. The number also identifies our test plan to be a smoke test plan. This is to assist in coordinating software and testware versions within configuration management).\n\n\nReferences\nList all documents that support this test plan.\n\n#####Documents that are referenced include:\n\nProject Plan \nSystem Requirements specifications \nHigh Level design document \nDetail design document \nDevelopment and Test process standards \nMethodology guidelines and examples \nCorporate standards and guidelines
686806
There is not one specific Test Case Format, it really depends upon the standards of who you are doing it for.  Every company has their own standards.\n\nHowever, just for reference, I would suggest the following format:\n\n1. Test Condition Description:  A short synopsis of what you are trying to test (and always test for things to FAIL as well as to work)\n\n2. Test Steps: This should be a list of detailed steps to follow in order to complete the test.  This includes all the setup required to get to that point.  If you want to test a program that is printing an invoice, for example...  part of the test case has to be creating the order/invoice in the software and getting it ready to be processed.\n\n3.  Expected Results:  This is a description of what SHOULD happen when the Test Case is run.  Some people like to put expected results after every step of the Test Case, while others put one Expected Result after all the steps have been run through.  It all depends on how detailed of a process you want the testing to be.\n\n4.  Actual Results:  This is a section where the person testing the Application writes in the actual results.  Sometimes they match the expected results, sometimes they don't.  If the two do not match, then it must be determined if it is a bug or the Test Case was written incorrectly.  Actual Results should come after all Expected Results (so if you are doing Expected for each step in the Test Case, you have to do Actual for each step as well)\n\n5.  Pass/Fail/Status:  Finally, I suggest a status on the Test Case.  This should indicate if the Test Case was Passed or if it Failed.  Depending upon the complexity of your application, you could have other statuses such as Passed with Conditions (like a message has a typo, but they don't want to retest this just because you have to change the wording of a message) or Failed Pending Review (they think it failed, but there will be a meeting to discuss if the bugs are critical).\n\nFinally, I think it's important to note that you have a Test Plans and Test Cases.  Test Cases are every single situation you want to test.  You can write general ones like "Add a Customer" to just see if functionality works, then you should have detailed ones that test specific functionality.  Remember, part of Testing is trying to BREAK the software, not prove it works.  So, some Test Cases may involve "bang on keyboard" or steps that you KNOW are wrong, but a typical user might do.\n\nThe Test Plan is an assembly of different Test Cases.  You can have a Test Cases that do some pre-setup of data and include those FIRST in your Test Plan so you don't have to include this setup in every single Test Case.\n\nRemember to be thorough, that is the most important part.  Think of EVERYTHING.  That is what makes Application Testing so difficult... there is no way that you can test every single situation, but test the most likely ones.  Test the limits too.  If you can enter a value from 0-100, test 0, 1, 99, 100, -1, and 101 as well as things in between.  Those are the most likely areas for bugs.
388022
A test for a computer product prior to commercial release. Beta testing is the last stage of testing, and normally can involve sending the product to beta test sites outside the company for real-world exposure or offering the product for a free trial download over the Internet. Beta testing is often preceded by a round of testing called alpha testing.
952028
testng what language, hardware or tool?
890914
The best tool you can use for testing web apps is your own browser. That is the same tool everyone is going to be using to access the web app too, so why not make sure that it is bug free using the tool everyone is using?\n\nNow there are a few tools for testing server-side code that you wrote for a web application. I have added several links to testing "frameworks" for some common server-side languages.\n\nHope this answers your question to your satisfaction.
9546
A 'beta' is a version still under testing.   \n\nHardware or software systems often go through two stages of release testing: Alpha (in-house) and Beta (outside of the company). Beta releases are generally made to a group of lucky (or unlucky) trusted customers.
670022
The QA Tester generally does not have to have any knowledge of the software being tested; the Tester follows testing scripts.  \n\nThe QA Analyst must be familiar with all of the software requirements and develop tests to ensure that the software meets those requirements.
426776
Alpha Test\nIn software development, your alpha test, will be a test among yourselves (the teams) to confirm that your product works. Originally, the term alpha test meant the first phase of testing in a software development process. The first phase includes unit testing, component testing, and system testing. During this time you will compress files, edit for misspelled words and unclear directions, broken links, and sync audio and video. You will also test your product on the lowest common denominator machines to make sure download times are acceptable and preloaders work.\n\nBeta Test\nIn software development, a beta test is the second phase of software testing in which a sampling of the intended audience tries the product out. Beta testing can be considered "pre-release testing." Beta test versions of software are now distributed to curriculum specialists and teachers to give the program a "real-world" test and partly to provide a preview of the next release.
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.
370687
For software engineering Following testing tools are used - \n\nLoad Runner \nWin Runner\nTestDirector\nVisual Test - Specially For Visual C++\nSQA Suite \nSQA TestFoundation for PeopleSoft applications \nPureCoverage\nPurify \nTestmate \nC-Cover , ObjectCoverage - coverage tool \nBoundsChecker\nObjectTester - automatic test generation\nTestCenter\nAstra SiteTest \nITEX - Interactive TTCN Editor and Executor
1016509
Software Engineering !!!
435500
Beta is a name used by software developers that want to test their programs out first- to see if there any bugs present in the programs that can be fixed. One can assume that they use the term "beta" because it's second-rate (or not quite the perfection they seek that is called "alpha").
746120
Can you be more specific?  Testing for what?
1015035
Beta is a test version to allow people to experiment/test what the maker is making. In most cases, it is software. It allows the maker to fix any problems the software may have on different systems to allow it to work without problems later on after the product has been fully released to the public.
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.
732098
Beta technology ? Beta is a term used for prototype software that needs user feedback to the developer, before the software is ready for use by the general public. During the Beta testing period, trial versions of the program are made available to "Testers", who use the software in a variety of environments, then send "Bug Reports" to the developer, so that they can correct these "Known Issues" prior to releasing the next version. Hope this helps.