what is software testing?
364874
It's the process used to identify the correctness, completeness, security and quality of computer software.
156489
Quality of software depends on testing. Also you have to make sure that requirment of softaware is fullfilled. Actually when you develop s/w you have requiremen specs, you have to match with final product to determine quality of software.\nThank you,\nMiral Patel
228401
Sure. It depends upon the features that you want tested. There are a number of automated testing tools available in the market. A majority of them are best suited for GUI based testing
588719
From all of the IT people I've spoken with, and my own observations, testing is one of the most dreaded tasks on any project. The other is documentation, and writing test cases would involve both. (!) It's also essential to the success of a project, so if you can tolerate or even enjoy that which others cannot, it may be a good niche for you.\n\nChris (an IT manager)
1071290
Software is basically an application you install on your computer; it's any kind of program.\n\nWhat do you mean by software projects and lines?
106336
Software testing is where you will have the test cases and scripts to you will follow them to verify if software is working as intended.\n\nBut Software Quality Assurance is the whole testing process right from What do we need for testing? How many people do we need? What environment do we need? It also includes the development of Test Plan, Test Cases , Scripts and all other documents.\n\nSoftware testing is a subset of SQA. I hope this is clear for you.
1058
Basically, its a test to see if a program or hardware setup crashes, usually over an extended period of time.
28904
A beta version or beta release represents the first version of the software that has passed system testing and regression testing.\nThe beta build is now ready for a beta test, in which it is tested through a limited roll-out to a production environment using live data and real users. The beta test is closely monitored by the software testers.\nSome development teams use the term beta informally to denote build of the software that is stable enough to be useful for internal demonstrations and previews to select customers, but not yet ready for release.\n\nAlso note that beta is the second letter of the Greek alphabet, being alpha the first letter *and* the first development stage of a program.
514671
These may help:\n\nhttp://www.google.co.uk/search?hl=en&q=types+of+software+testing&btnG=Google+Search&meta=
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.
41028
"Beta" is the name given to a pre-release version of a software product. Normally the beta version is used for testing purposes and is primarily intended for trial by users who have the expertise to provide quality and improvement feedback. Beta software is in most cases made available as a download from the website of the company that originated it. Beta software can be unstable and the author usually issues a disclaimer to this effect. To prevent a flawed product from being spread to widely the beta version is commonly made available for a specific period of time beyond which it is rendered unusable.
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.
614603
The computer science discipline concerned with developing large applications. Software engineering covers not only the technical aspects of building software systems, but also management issues, such as directing programming teams, scheduling, and budgeting. Also, Software engineering is the profession concerned with creating and maintaining software applications by applying technologies and practices from computer science, project management, engineering, application domains, and other fields. \n\nAs of 2006, the U. S. Bureau of Labor Statistics counts 960,840 software engineers holding jobs in the U.S.; for comparison, in the U.S. there are some 1.4 million practitioners employed in all other engineering disciplines combined[4]. There are estimated to be about 1.5 million practitioners in the E.U., Asia, and elsewhere[citation needed]. SE pioneers include Barry Boehm, Fred Brooks, C. A. R. Hoare, and David Parnas. There is extensive debate about what SE is, who qualifies as a SE, who sets the standards, etc.\n\nHence, you can achive so many things if you learn Software Engineering.
101669
Testing a software component when the source code of that is not available is called as black box testing.\nNormally third party components such as activex controls or .net components are tested as black box, because their source code is not privided.
633705
Here is a complete definition with details...Too much info to type it all in here...\nhttp://en.wikipedia.org/wiki/Software_development
570441
Manual Testing is done manually by tester by putting input and checking output.\nAutomated testing is done by using tools like Loadrunner, Winrunner there are too many tools.
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.