Tag Info

To put the other answers in context, there are some related ideas here, which may be stomping on each other. Defect insertion (or discovery) -- reference to which phase of system (e.g., requirements development, design, development, implementation, integration, test, sustainment) a defect was inserted/injected (or discovered) in the product. So a defect ...

You might try these things. encourage people to think about the last time they consulted a testing standard or a canned process document and found it even remotely important, helpful, and useful ask people if they would use the same approaches to testing a medical device, vs. a game, vs. a financial institution, vs. an online dating service ask people ...

Measuring ROI of just about anything is subjective because it often depends on context. For example there are many test automation ROI calculators and formulas running around the Internet, but all assume that we all automate our tests the same way, and they fail to take into account intangible value from automated tests (e.g. confidence, stability, etc.) I ...

If you are running a service or a platform (e.g. operating system), then MTTF and MTBF are very important factors in software and have been used for quite some time to assess reliability usually via some form of stress testing. One of the primary purposes of stress testing is to find the MTTF (mean time time failure) which generally occurs due to memory ...

According to the Windows Installer blog: Multi-part CABs can get the total size of a set of files past 2GB, possibly to 64K * 2GB 64K * 2GB is 128TB. I expect the maximum file size you can upload will be dictated by something else - e.g. the amount of storage on the server or some kind of upload quota.

Couldn't I just run the (in this case small) program then and test it manually? Yes, that can be considered to be an integration test. The question is how often do you expect that test to be repeated, and how much effort will it take to automate the process. If you think that test needs 5 minutes, and automating it takes 5 days, then you can make a lot ...

An injected defect is adding defects to a system on purpose during testing, to test and verify that the system behaves as expected in those situations. This is good testing practice, and nothing that should be reduced or avoided. Examples of such defects can be: Introducing unreliable network traffic. Testing with a full hard drive. Testing with some ...

I would list down based on my previous experience - Replication Test Effort using SQL Server. My scenario was Transactional Replication. I am not aware of Postgress DB but there should be simlar jobs equivalent to jobs/monitors provided in sql server. What all areas to test Initial Setup Configuring Replication, Running Replication Scripts on the ...

Yes, it can be measured but NOT always quantitatively ! Some examples which I have had experience with - Quantity - Man hours/$s saved by automating a set of regression tests which were previously taking X no. of man hours Further to above, those Man hours saved yielded in these number of new bugs detected( because testers could focus on "other" ...

I used SVN successfully with RFT Java test scripts. The Subclipse plugin does work however you need to ensure you version control all the files, not just the Java files themselves. Tortoise SVN also works well outside of Eclipse. That was over a year ago so I am a bit rusty I'm afraid. Because several files are updated automatically when you are editing ...

I would understand this to mean either fault injection which @Anders covered in his answer or the same thing as defect seeding or error seeding. Error seeding is a way of implementing a metric for checking how good testing is done for a system. It would be nice to know how large percent of defects the testing is finding or how many bugs still exists in the ...

There are many ways to approach this, and what is "best" will depend on your skills and point of view. Google's BITE record and playback chrome extension might do the trick. If you are looking for an open source solution that requires development then you should look into using selenium http://seleniumhq.org.

You're getting some good answers on the first part of your question (what are injected defects?) but all seems quiet on your second question (how can they be reduced?) Sound software engineering principles should help, such as: Know your requirements Perform reviews Plan thorough testing early As others have alluded to, early detection is perhaps more ...

Selenium is a good open source tool for automation. Cucumber/Watir are other alternatives. Sikuli is a screenshot comparison tool that can do a lot more than just compare pixels. We are evaluating it for use with some of the Flex components in our application. AFAIK, all other automation tools (at least the ones I know) require some modification at ...

The problem with general approaches is they are just that - general. That may or may not relate to you at all. So the most important thing is to understand or be prepared to learn as much as you can about the underlying system and software - in your case Postgres and some flavor of *nix. I, like Siva, have tested replication on SQL Server using ...

In response to BJ Rollison: To name but a few attempts to get something that I'd call "standardization across individual testers": http://softwaretestingstandard.org/ http://www.tmap.net/Home/ http://www.tmmifoundation.org/ http://istqb.org/display/ISTQB/Home ---Michael B.

Bishop and Bloomfield have proposed a method of predicting long term reliability growth in software. It is based on an initial assessment of faults. Their work is very easy to understand and follow and later works look at estimating software defects by various methods. A large set of their papers can be found here. ...

Wikipedia has the best answer for this one. Reliability engineers / design engineers, often utilize Reliability Software to calculate products' MTBF according to various methods/standards (MIL-HDBK-217F, Telcordia SR332, Siemens Norm, FIDES,UTE 80-810 (RDF2000), etc.). However, these "prediction" methods are not intended to reflect fielded MTBF as is ...