what is the main defference between software testing and software quality assurance.?
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.
820049
Well the term quality control can be applied to any lab environment, its what you do to make sure that the experiment or equipment is running smoothly.  For an experiment or industrial process, its something that you do that you already know the answer for, so you can tell if your setup is running correctly.
68817
Heh.  If the code is in good shape it should already have lots of automated tests.  If the code has lots of tests, you should be able to change it with a reasonable assurance of not accidentally breaking anything.  If you can change it, you can refactor it.  If you can refactor it, it should get steadily better.\n\nIf the code _isn't_ in good shape?  Start figuring out how to write automated tests for it; the rest will follow naturally.  Michael Feathers' book "Working Effectively with Legacy Code" is a good reference for this.
499117
A beta is a trial or pre release version that is being tested usually by volunteers. If can be prone to difficulties while the programmers are debugging it.\n\nYou get to try the newest things in return for running a Beta.
948411
The stage of testing that is being performed on the software.\n\nAlpha testing is generally done "in house" by the company that is intending to release the software, by the software company employees or contractors.\n\nBeta testing is after Alpha testing and is a phase generally moved into when a company wants to see how real users will interact with the software.  It's helpful for the company to see the things it didn't catch in initial (or Alpha) testing.  Generally Beta testing leads to either Release...meaning they fix most of the bugs in Beta and they go ahead and roll out or sell the software...or the third stage of testing, called Release Candidate.\n\nRelease Candidate is sent out, often to people who actually pay for the software because they have a large business need which the software will help fix.  Even though the company buying the software is aware they're going to be helping the producing company test their software, it's still a good relationship to enter if the cost of NOT having the software outweighs the cost of dealing with pre-release "fully" tested software.\n\nRelease Candidates can also go through versions, like RC1 and RC2...coincidentally, Windows Vista is on RC2 now (I think) and that - at least in Microsoft speak - means they think they're almost ready to roll this software out to the general public.
195978
Test Run seems to have a lot of nice stuff.  I recommended it to our QA people but they didn't seem too interested.  But I bet you could at least look at some of their samples.
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
83394
Testing the programming by essentially trying to break it.\n\nIn other words, instead of testing the program to see if it simply meets the criteria established in the design, the tester is literally throwing the kitchen sink at the program to find its weaknesses. I like to think of it as "real world" testing.
894211
forget that test, they always find some "faults" only to animate you buying a useless system tool. if the PC is working normally why should you change something?
459445
System evaluation by the analyst, is very week, since the analyst is the one who knows exactly how the application have to work, and he will do every step exactly the way it is supposed to be, and that way is dificult to discover bugs or wrong functionality.\nSystem evaluation by an independent evaluation team, can be a good option, but only if the evaluation team knows very well the functionality that is required by the system.\nSystem evaluation by the client organization, should be done at final stage, and it's supposed to be done, where you and the evaluation team have done the work and you are pretty sure that there won't be almost any errors.
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.
664477
Several topics to research:\nWhite/Black box testing.  Performance testing.  Regression testing.  Use case scenarios/testing.  Product defect lifecycle.  Issue/problem management and tracking.  Some industry standard QA tools to consider....SQA Robot, Mercury Interactive (WinRunner), Silk.  Most QA technicians need a solid understanding of the development and issue management lifecycles as well as a decent amount of scripting knowledge.
353698
Actually the two are very different functions.\n\nQC is verifying that approved standards and procedures are being followed properly to produce a certain level of quality. Generally sampling or testing is employed to verify acceptable levels of quality.\n\nQA is oversight and assurance that a QC program is in effect and being properly administered.\n\nI am the QC Manager for my company. The company we provide construction and maintenance services for (our client) employs their own QA folks to oversee my department to make sure we are doing our job.
443623
I was in a system migration project some years ago. Basically you should be able to track success of project during testing phase. So if you are following any standard SDLC say the 5 basic steps of system development, the testing phase will have your evaluation and after go-live you will continue with your audit. You evaluate existing performance against expected results.
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
65357
For me - the only real differences are the installer and included packages.  You can get any packages and install them if they are not included so they are all essentially equal i suppose.  I prefer slackware though and it is great for development.
1016509
Software Engineering !!!