jilolens.blogg.se - Oracle scratchpad

Oracle scratchpad manual#
Oracle scratchpad code#

identify test-infected people outside the mozilla community and ask them to help.identify people in the mozilla community who are already test-infected.can walk the state transitions and detect failures other than asserts or crashes.allows for high volume automated testing.use model-based test scripting when possible.

Oracle scratchpad manual#

do not rule out computer-assisted manual testing (no automated oracle).focus on oracle (how do we know the test passed or failed).data-driven (data separate from test code).follow list of principles for automated testing.

or choose 1 of no more than 3, if 1-size-does-not-fit-all.

common invocation and reporting formats for all tests.

create test infrastructure architecture.

xulUnit, jsUnit, jsUnit (yes, there are 2), xUnit, FIT.

Catalog all existing test suites and/or test cases.

each group shares domain knowledge with the others.

toolsmiths maintain the infrastructure, and find/adapt/use tools to solve problems.

we need involvement from toolsmiths and developers and testers.

they function as executable specifications for the code, and can replace some documentation and usage examples.

Oracle scratchpad code#

immediate and precise feedback - written close to the code.developer unit tests are typically not-very-powerful tests.We should not extinguish this valuable channel of information. feedback from user community is unstructured and somewhat unpredictable, but incredibly useful.if code is more testable, then tests can be more powerful.if developer finds something that is difficult to test, then developer can make code more testable.automated developer testing works only if the developers are writing the tests.replacing a test that is useful to person A with a test that is useful to person B but not useful to person A is bad - just add the new test.There are lots of different types of testing, each providing a different type of information and involving different trade-offs.Testing provides technical information about the product/system under test.This page is the first cut at collecting Dave's plans and investigations. Not just end-to-end automated tests, but unit tests, module tests, test harnesses, test reporting infrastructure, and anything else that lowers the barrier to creating new code that gives someone feedback.ĭave needs help. Dave Liebreich is interested in creating running code to test the mozilla codebase.