Well, its been over a month, so…
- Is there a way for me to incorporate my DoFixture methods into the table wizard to aid in creating tests? No, the table wizard only helps with ColumnFixtures.
- dogtail: “dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. dogtail scripts are written in Python and executed like any other Python program.”
- FitRunner: an open-source eclipse fit plug-in
- JPDFUnit: java based unit test framework for working with PDFs
- Podcasts from Agile 2006
- 12 Questions with Mary Poppendieck
- On including test code in production releases – About 30% of the circuits in a typical IC are there for testing purposes. IC manufacturers could significantly increase their yields and therefore profits if they took out these testing circuits. But that would also lead to unacceptable defect rates.
(Yes, almost 900 messages and I found 2 things that interested me. As my workload moves more to management instead of testing, I find myself less concerned with little automation flamewars, etc)
- Some criteria for accepting requirements:
- Clear and properly stated: clarity of process, functionality and expectation
- Complete: the description of the requirement, per se, is complete
- Consistent with each other: avoid contradiction; conflicting requirements; one defeats the raison d’etre of the other requirement. It could be also that, the pre-determined expectations do not match with the requirement being called for.
- Uniquely identified: a distinct label or handle assigned to it.
appropriate to implement: basically the feasibility of accomplishing the functionality/process expected
- Traceable : trace to a specific functionality or a business process.
- CMMi v1.2 Production Suite is now available
- A Case Study in Root Cause Defect Analysis
- Seven causes of defect
- Communication Gap -Due to lack of exchange of information between various internal groups (QC, Multimedia etc) or with the client
- Oversight -Due to factors or aspects of design overlooked during development (Carelessness)
- Understanding -Due to a lack of understanding of the particular concept in question (Unclear product/project/process requirements)
- Rework -Unintended errors caused during rework of the work product.(Bugs that moved to 2nd round of testing)
- Lack of Training – The person is not adequately trained on product features/roles/responsibilities/process requirements.
- Tool limitation -Errors attributed to limitations in the tools used for developing the work product. (Technically not possible)
- Bug in existing code -Errors in the source code of the base project.(Maintenance/Enhancement projects , reusable components, etc)