Tag Info

Hot answers tagged

7

Mutation testing is generally interesting from an academic perspective. I have never seen or heard of anyone using mutation testing on software that is delivered to customers on a schedule. The time and expense involved in mutation testing is huge compared to the perceived value returned. In complex projects with several developers contributing to the ...


7

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 ...


7

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 ...


6

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 ...


5

I work for a small company with four developers and two testers. Our product is a web-based application that we deploy to Amazon EC2. The application targets holders of a special kind of bank account. I will describe the process we use with external participants, i.e. with participants who are not our employees (we also run informal usability tests with ...


5

I'm the author of one of the tools for Java (http://pitest.org). I have found mutation testing useful in practice, working on large legacy corporate code bases and smaller test driven projects. I've seen a lot of dismissals of the value of mutation testing such as Bj Rollison's answer. I generally don't disagree with the points he makes, however some ...


3

I'd second Phil's plug for the Software Testing Club website, and encourage you to seek out the mentoring group on there (although it does appear to be pretty quiet at the moment - perhaps it might be prodded back to life? I recommend it because that's how I ended up receiving some absolutely invaluable mentoring from Michael Bolton. (Who is, incidentally, ...


3

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 ...


2

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" ...


2

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 ...


2

They can - and should be. Sit with the designers as they develop their wireframes and prototypes. Help them out with their scenarios and personas. Make yourself a cardboard iPad and try out the layouts - see here for a real world example ( and an aside, I dont really understand what the difference between QA testing and usability testing is - well I sort of ...


2

It is certainly possible, but it might be easier as a contractor, with a company helping you line up projects. I got started in QA working for a company that did this very thing, lining up contracts with clients for test work, then finding Automation or Manual resources to complete the contracts. Some of the projects were short (just a couple of weeks) to ...


2

I have worked in two different scenarios: a large project to develop a scheduling app for a government agency and an established commercial product. In both, usability was integrated into the testing but in very different ways. For the large development project, we invited local representatives from the customer into our test lab during development (i.e. an ...


1

Shameless plug for The Software Testing Club website - has good list of tester blog feeds to read, discussion area to start discussions and join in with. Trying to answer questions and help is a great way of finding out what you really know. ( same principle for this site and SQAForums ) Are paid courses possible ? If so the AST courses are good for ...


1

My answer is 2 parts, first in direct response to your question: You should definitely keep usability in mind while testing your product. Just because the product matches the specification, does not mean that it is intuitive, simple and concise. If it's difficult for you to understand or use, then you can pretty much bet it will be even more difficult for ...


1

I've been involved with all of the above. In my first QA role, I managed a team that was responsible for ensuring compliance to UI Standards. At another company, we did somewhat formal Usability Testing, bringing in existing customers to explore the application's usability in an inexpensive manner: ...


1

Mutation testing has been used in some small systems e.g.: see article "An intuitive approach to determine test adequacy in safety-critical software". Here's the abstract: Safety-critical software must adhere to stringent quality standards and is expected to be thoroughly tested. However, exhaustive testing of software is usually impractical. The two ...


1

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 ...


1

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.


1

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. ...


1

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible