As a person with experience and training in software testing, I decided it was time to record at least some of the information I have accumulated over the years. Reasons: to concentrate the substance, give access to information for people in my teams and to all those interested in the field can read and get ideas. The information here is relevant both for people rating new to the field and to experience. The site and Htmfliitim are free and in good faith.
Not all bugs, of course, rating are the bugs: - Some bugs are closed as Invalid, ie the steps leading to incorrect or expected result is correct, or that the environment was discovered bug is the right environment and more. - Some bugs are Msthazrim, some are WAD - Works As Designed. - Some bugs just are not corrected rating because they do not depend on us, or low impact bug against time and risk his amendment. So some bugs should be closed. The question is - who closes them. Do we trust the key? Hmm, I think not. Is the reviewer can close? Sometimes yes, but not always. Maybe he does script in non-region system he knows. Sometimes he just might believe the key. The problem is that there is little chance of losing that important bugs. For example here is a real case: We are working in a test environment. At that time we used the SSL environment, but the problem is we did not have the above-mentioned certificate environment. It means we get an environmental assessment is not really protected. Hsteig'ing environment however we had the original certificate. Checks examined Vsteig'ing received the message above " for, as was not supposed to be Vsteig'ing. He opened a bug. Key, which is incidentally one of the best and head magnifiers that - I used to work with him, canceled the bug on the grounds that the notice is due to the environment. Happens. Reviewer, who may also be responsible, took the message key, perhaps because it was known that the key is not to ignore the specific bug, closing rating the bug. Then came the critical bug what-production users get an error message of the SSL Certificate. By the way, to this day I have not told this key. Anyway had to understand our environment, which has five analysts rating and sometimes twenty checking, debugging may be lost, and we can not afford it. So we put a process with two main points: a. Must not in any case the developer to change the bug status of a terminal (as Invalid, Will not Fix, Works For Me and Domiihm). If there is an option to back it up permissions - all the better. In. Also checks can not close a bug, just an analyst, and the analyst responsible for the domain. Where there is no distinction between the analyst checks, just checking it Ratz expert on the subject or can close a bug. How to do it? By Status suitable bug (eg in bugzilla by adding a Keyword). Reviewer adds status after the key convinces him to remark rating appropriate bug report. ever on charge developed suitable filter, see the bugs that close and decide on the next step - to close or reopen., I want to remind readers learned, we can and must sometimes share the product manager deciding how to proceed bug. Not everything rating is within our jurisdiction., I can say that almost daily we reopen bugs that would otherwise disappear in the system.
01. No specific role of QA 02. 03 continuous feedback. Provide the customer with exactly what they need 04. Communication and Knowledge 05. Simplicity 07. Willingness to change
Load - STD - a simple document Load - STP - a simple document STD example STP orientation and Home STR - System Testing Report TD: Text field generic tests how to measure team leaders of testing generic text field example of the life cycle version with explanations Glossary of -ISTQB document management integration testing integration testing gate 2 Presentation guidelines: What are the tests and how to do it? Check Liszt's the end checks on a particular schematic process of project management with a client
100 good Blogs of tests James Bach - Satisfice, Inc QTP Advanced, and Hebrew! sqatester - information about software testing StickyMinds - Magazine on tests Storm Test Star - Magazine Experience on testing Testing American organization quality very informative site (was originally brought by Kobi Halperin) invoke, Tzik bandits rating and templates. material includes a check bandits and more ... a technique for early detection of bugs: Poka-Yoke Techniques rating good articles on the subject of classification tests Bugs: ODC answers on the topics of testing and Utilities
A perhaps less relevant for testing, good designers and developers. Send a link of your site and you get screenshots of how the page looks every possible browser testing of applications in a variety of cell phones and network! Different versions of IE one application rating testing tools comparison rating between the test data generator free testing tool recommendation list tact
Who is responsible for monitoring system malfunctions? What happens to the bugs that are not really bugs? Or: risk of losing real bugs matrix regression testing on different configurations for critical reading of the requirements of the product manager / Hmrkting preparation rating for a new build
So what is the difference between a successful startup that one - I promise I have not forgotten the issue of launch, but something short that I wanted to share with you: As part of The Startup Nation Feed, we ask the same question every week the guys startups ...
Strategies for testing mobile applications - insights and principles - in the past I have written about the difficulties of managing and testing mobile projects. In this post, I'll give you the latest insights which may help the development and testing will be carried out entering these days ...
New Tests
01. Acronyms and concepts rating 02. Why should software testing? 03. Definition of Software Testing 04. What do you mean had been replaced working properly "? 05th. Two Major Categories in software testing 06. Types of tests 07. Progression and Regression 08. The issues that checks Web should know about? 09th. Practice "wet" rating test your skills 10. Matrix of regression testing
01. Cost
No comments:
Post a Comment