Hot answers tagged test-management
10
Welcome to SQA, Rosa. I am not sure your question makes sense; QA is an abbreviation for "Quality Assurance", and often is used as a synonym for testing. ISTQB is a type of certification for testers.
See also Do ISTQB/ISEB Testing Certificates prove someone can test? and http://en.wikipedia.org/wiki/Caps_lock.
9
Automation is using software to test software. Testers use automation for the same kinds of reasons that other professions use automation: to do things in a more reliable, repeatable way than we could do with people.
There are other reasons why you might use automation. For example, it may save time and/or save money, although if it is done in the wrong ...
8
What value is "yesterday, today, blocking" to this team of testers?
Presumably they have similar scrums where they present the same information to the functional team they are assigned to. So you may be asking them to repeat what they have just said, or will soon say.
Perhaps you instead want to focus your meeting on "what is important for other testers ...
7
I'm going with my favorite response here: it depends.
Sometimes the decision is made because that's the language the tool supports. Sometimes the language is a flavor of the language used by the development team - this often happens where there's an expectation that the development team will be writing at least some of the test automation code. Sometimes ...
7
You should not edit the tests to pass. There are still defects in the product, and running the tests and having them fail on those points continues to provide data that the issues are not fixed.
Since the development team has accepted the bugs and scheduled (although not solidly) them to be addressed, modifying the tests to no longer report the defects ...
5
One possibility here is to build into your testing the ability to flag a failure as a "Known issue" which is then reported with each run of your automation.
I've gone into more detail in my answer to the question user246 linked - I'd recommend you check into my comments and the other responses there.
5
Test automation is a tool that can be used to remove the need for humans to have to execute the same checks over and over again as the software is changed as it is being developed.
I use the word "check" as automation doesn't do what a manual tester can do, it doesn't question, or think and make and disprove hypothesis on what bugs exist in software. It ...
5
Not saying that it's cheap, but, tools like OneNote tend to fill this void very well. We use a notebook for each application. For projects, we use Tabs/Sections for Modules/areas, and for operational type changes, we use a new section for each Release. Each session takes up 1 page. These get stored on either a sharepoint or in a shared folder that we all ...
5
David,
I've thought about this exact question quite a lot and I'm optimistic that I'd be able to help share some tips that you'd find useful. Unfortunately, explanations in a few paragraphs may not be sufficient to answer your question in detail. I'd be happy to talk by Skype today if you want to talk; I'll send you my Skype details via LinkedIn.
What ...
4
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 ...
4
Use whatever you are comfortable with. I'd suggest starting with something basic for recording notes like Notepad++. The important thing is to be able to keep detailed notes about your session, to setup a session charter, etc. Once you've got some practice with it, you can see what works and what doesn't.
I've used Rapid Reporter and Session Tester as ...
4
This is where continuous integration comes in very handy. Generally the simplest form of continuous integration is automatically building and executing unit tests every time code is checked in. This is to reduce the amount of time it takes to discover possible build breaks or code level defects.
Similarly, many people extend continuous integration to ...
4
I'm going to go out on a limb here and say that what you have is an ad-hoc development process rather than an agile one.
Here's where I'd start, assuming that you have the ability to work with the programmers and project/application management on this (you can get a lot of it even if you don't have that ability).
Who - Who is the intended and actual user ...
3
A test log is simply a log used for testing. ISO 9000 compliant timber companies typically have detailed guidelines for the structure of test logs. For example, they must still include bark, must be between five and ten meters long, and between 50 and 100 centimeters in diameter. Like production logs, test logs must have visibly apparent concentric rings ...
3
What you need is to improve your Requirements Engineering processes. There are commercial tools that help in this area (I have worked with Doors some years ago), but I don't know of any open-source alternative I could recommend.
The problem is that these tools and processes are very "heavy weight", and in my opinion, achieving requirements traceability ...
3
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 ...
3
Don't know how reliable they are, but some of my colleagues recommend this site which they used before the exam (and they did all pass):
http://istqbquestionbank.blogspot.se/2012/01/istqb-foundation-sample-question-paper.html
I haven't tried it myself though.
3
Testlink is still the leader a lot on the open-source market however there has not been much changes in the last years and some people start saying it's a dying project :( maybe just a rumor but anyway it's not been very active recently... IMHO XStudio is the best choice by far. It has great features and it's growing fast. It has even better features than QC ...
3
Welcome to SQA, David. I suspect many of us have been in the same position -- I certainly have.
You did not ask for advice on what to automate, so I assume you are mostly interested in how to document and execute a test of so many options. One way to reduce the effort is to investigate how the 46 options are implemented. The more code they share, the ...
3
Given that a scrum meeting should be really quick, how much support will this actually give the testers ! Why are you calling it a scrum, can't it just be a meeting ? Also, if you are 'managing' the testers then it seems to more of a meeting than a self-organized scrum....
Not saying your idea is wrong, not sure that calling it a scrum is the best ...
3
Even though an answer was already accepted I felt to offer another perspective:
You should not run a scrum for the testers only.
Effective scrum teams rely on their ability to self govern and self organize. So each team will handle things in their own way. If a tester has an issue, he/she should bring it to the scrum master and work it out in the team. ...
3
Ok, here is what I think you are asking: Will QC help you track the development/test status of your software delivery and provide an effective report mechanism to your management?
First the answer: No
Now for what I think is the implied question: What can I do to help report the development/test status of my software delivery?
Best answer I have seen: Low ...
3
Depend on industry, domain and whether companies give out titles or not
Some companies will have a rigid structure where you need X years before you get a title change
I've known 'test managers' who have 2 years or less experience and you can find people who've worked for many years who are happy just to be called testers
3
The short answer to your question is that if the same person does both the development and the testing, he's going to bring a lot of assumptions into the tests. On the other hand, he probably already knows the weak points and how the code works, so he's got a lot to offer in the testing process too.
It doesn't sound like you have dedicated testers, so ...
3
Issue Reports (Bug Reports) are one of the main communication methods that QAers use.
You are creating a statement to your stakeholders - "I have found what I think is a problem, and here's my clear explanation of what it is and how you can see it too. Please look into this".
Understand the Audience for the Report
It's important to know who is going to ...
2
After doing a few such evaluations myself in the last couple of years I can share my experience.
The two top tools found were QAComplete from SmartBear and QMetry. They both have strengths and weaknesses so depends on your specific requirements one of them would suit your team more.
For a single tool environment (so requirements and defects managed in the ...
2
Yes, it is possible to do this. Within the Analysis View, go to "New Excel Report". Excel reports are the most flexible feature of the Analysis View, because they allow you to write SQL queries against the ALM database to extract any detail you want, at any level of summary. You can then use Microsoft Excel itself to generate charts (if you desire) or pivot ...
2
We use SCTM and we use exploratory testing alot.
We use SCTM to track the areas we've tested by creating manual test cases that is really no more than a brief description of the area/function that we intend to test. Sometimes we also refer to charters when we use SBTM.
We then use SCTM to track the execution of these exploratory tests - works well for us, ...
2
Particularly in a small company, go to the readers of the report to find out what they need for it to contain.
Usually, people don't want to hear about your testing work, just the results. Those results might include any open, but deferred, bugs. It might include release notes. It might include features added. Etc, etc.
Do others know the definition of ...
2
Are the tests at least categorized by product, feature and separated by unit/integration/functional? If not, that would be a good place to start to start before trying to figure out what coverage they provide.
One possibility would be to run code coverage on your product while executing the tests. This could give you a good indication of what the tests do ...
Only top voted, non community-wiki answers of a minimum length are eligible
