Tag Info

You could setup personas which are designed around real world of users. We have found this quite useful and it really helps to provide a fresh perspective e.g. Today I'm going to be Andy, the super user of the system. Andy is very sharp with numbers and is the user that is responsible for the administration of the system. He enjoys watching sports on ...

Being QA Manager with about 3 years of experience, I just give my team mates testing tasks, which are NOT related to software, e.g.: Compose test cases for blender / vacuum cleaner / etc. - any kind of familiar device / equipment. This results in brain refreshing, and for the cost of 2-4 hours I get team "reloaded")) The same is applicable for testing such ...

I think the simple answer is, do something else for a while. Our jobs require a lot of repetition, and we automatically develop habits in response to repetition. That behavior is a deeply ingrained survival technique; habits allow us to do things quickly without thinking them through. Sometimes those habits allow us to discover new things, but other times ...

You could try the 'tours' concept and try out different tours of the software. I'd also disagree somewhat with your premise - the more you use a program the more you notice any slight changes. You also understand more how all the parts interact which in turn gives more ideas. I think at the start you may notice more but they are shallower than ones you find ...

allquixotic, How important is it that you get these string correct in all situations? For example, if this is a life-critical application that depends intrinsically on the correctness of your strings (the difference between "Send police to the Town Hall" and "Send fire equipment to the Town Hall" for example), then you must do a deeper dive. Consider ...

Tracebility matrix is a tool. It doesn't have any inheritent value, but it might be easiest way of mapping certain kind of relations between tests and requirements. As with any other tool, if it seems to work well, use it. If something else fits better, use that. If the tool nearly fits your need, modify it to give what information you need. If testing is ...

One approach is to actively recruit team members and other stakeholders for testing of the product. I have found that it is useful to try different approaches and use whatever works best with each person, which can include: Paired testing with a code developer (emphasize the thrill of having a function work on the first build :) ) Asking a content ...

I have never seen such a matrix and never heard of it before :-(. Your goal: Which requirements is almost never tested, and which is tested extremely often? can be achived by agile/technical means: Using Behavior driven development bdd as automated test for a userstory to verify that it is complete and still working. There are code coverage tools ...

A test plan is worth creating if there is something that needs documented testing. It may be frustrating to see a test plan with only a few steps, but if you realize the purpose of the necessity of documentation, it doesn't matter how small the test plan is. You should include whatever it is that needs testing. Whether it's an anticipated UI response to ...

You could also change your testing approach. In my experience, 90% of time spent testing is Exploratory. this tends to get dull and repetitive. What I then started doing was changing my point of view or testing strategy. Try something in the lines of BVA. (Boundary Value Analysis). Obviously certain test strategies wont work on all types of software. It ...

Here is a link to a pdf article "Pairwise Testing: A Best Practice That Isn’t" (http://www.testingeducation.org/wtst5/PairwisePNSQC2004.pdf) by Patrick J. Schroeder and James Bach that discusses pairs testing and random testing. In essence, it promotes having multiple techniques in your toolbox when approaching this type of problem. Hope that helps!

Welcome to SQA, Teague. Your test plan is part of a feedback loop. You convey something about the project to whoever is testing. They test the project, find some problems, and fail to find others. You incorporate what you observed into how you write your next test plan. It is all about paying attention and being open to changing what you do according to ...

There are 2 plugins: Plugin to export requirements from word document to QC Plugin to export requirements from excel document to QC Once you install these in your machine, you will get options to 'export to QC' when you open the respective application. The pre-requisite is to have a properly formatted document (either word or excel). It will contain ...