what is regression testing related to qa
206864
When any device is designed it has to be tested.  But when it is changed, the testing rules can be slightly different.  Obviously the portion of the design that was changed has to be tested.  Regression testing is testing other portions of the design, not necessarily directly affected by the change to ensure that they have not fallen out of spec.
419342
What testing tools you are talking about exactly?
467004
Sounds like you want to use a database like Filemaker. With a database you can create custom reports that could be used as tests.
334525
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.
61389
Try www.txdps.state.tx.us/psb/testing
85519
Regression analysis is very complicated mathematical/statistic analysis that is very difficult to describe easily.  R-squared is a measure of how closely an investment tracks the S&P 500 or other index.  While I am not a great fan of investopedia.com, they give some answers in this case.\n(These comments refer to investment analysis, regression analysis is also used in other fields.)
549783
It means that the startup built in test detected a problem. Could be memory.\n\n**********************************************************\n\nDid you get this solved??
338397
Regression (any kind of regression) is used when there is some kind of relationship between the outcome (response) and predictor variables. There will be a change in the standard error estimates of the regression coefficients. But I wouldn't expect much of a change in other aspects of the regression. The best way to check to see if there is a big change: try fitting the model with and without the predictor that uses the same question as the reponse. If there is a big change, then you'll need to decide if the predictor is of significance to the survey. In other words, how important is this predictor to the understanding of the survey? If it's important, then keep it. Otherwise, don't keep it. But you'll have to decide. Model building is an art and science.
656175
This is a very difficult question to really answer correctly. According to Godel's incompleteness theorem, a system is either complete or inconsistent. Although Godel proved it for the natural numbers, i have taken the liberty of using it as an analogy for software systems.\n\nA practical way to proceed is to test throughout the life cycle and to correct errors. As the software gets used and errors get fixed, (without introducing new errors), it becomes more reliable. The existence of various software environments (different operating systems, transaction monitors, database systems, interfaces to other applications and services, etc.) complicates matters. Particlarly when you have little knowledge and/or control over the environmental systems and software.\n\nSo what to do about the initial and subsequent releases. One way is to classify errors into severe, medium and minor. The classification depends on the application and impact of the application. Then have a release policy depending on the number and type of errors detected in testing.\n\nTo illustrate, consider the following applications:\n\nreal time flight control software for a passenger aircraft, passenger reservation software for airlines or trains, on-line stock trading software, word processing software, chat and email software.\n\nClearly the societal impact of errors in the above applications differs considerably.\n\nSome organizations also use quantitative models to predict residual-error distributions based on on-going test results.\n\nTesting, maintenance and support are part of the software life cycle and i think its very difficult to say "i've tested enough", simply because it's difficult to define "enough".\n\nTo build and maintain good software you need good requirements and analysis, good design which is maintainable and testable, good practices, good tools, good environments, good infrastructure, good communication and most of all good people.
91122
Test and refactor, test and refactor.  The idea is that you find a few lines of code that you can understand, and try to figure out a way to write a test for just those lines of code.  Once you have the test in place, then you can try to rewrite the code so it is simpler and clearer to understand.\n\nI don't know of any unit testing applications for Fortran, so you'll probably be best off writing your own test programs.  But I did link to a page that might be relevant below.
562780
Try http://qualitybase.org It's free!
206499
I really don't know of one off the top of my head, but here is a site I came across once. I don't know if it works. Good luck.   http://members.aol.com/softwaresc/stats.htm
180201
http://www.mcse.ms/archive217-2005-5-1645242.html\nhttp://www.techspot.com/vb/topic47729.html\n\n^^ Those links will take you to forums that talk about those specific errors.\n\nGood luck!
332730
There are a lot of Software Testing opportunities present in bangalore as well as in India. you can go through a software testing course and apply for job by posting your resume in job sites like naukri.com. But testing also needs some experience. So try jobs on functional testing,software packaging testing which does not require much experience and background in testing. Some sites or yahoo groups where the software testing jobs gets listed are
324988
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.
11287
i am currently an AS400 programmer and I am evaluating the turnover software package from softlanding. They also have one called testbench which uses lpars to separate the box into prod and development environment
520182
Check this page\nhttp://www.evaluationengineering.com/archive/articles/1004/1004conformance_test.asp\n\nIt will give you the right info.