Test Information Space

Journal of Tech, Testing and Trends


Posted by cadsmith on May 31, 2009


Consider whether an ideal tester can emerge from a distributed repository such as Test Info Space, or what a utility of this nature would be like. The effort might lead to a knowledge base to support development and validation efforts, if not as straightforward as a spell-checker for an editor, then at least to assist in browsing, documentation or presentation. A private cloud or internal network might add or replace web content.

Assume that the purpose of the tool is for debug, test and diagnostics. It would have some form of search, e.g. keyword or semantic, a Q&A ability or directory, recommendation generator, a logging mechanism for tracing or reuse, and scripting for automation. It is a composite of sources including history, state of the art, and research. Users can lookup concepts to find descriptions and supporting links, or test cases to match solutions by example. It can provide comparisons by similarity, counter, or uniqueness. This might be done at a high level of methodology or fine-tuned by fields, domains, characteristics, indications, and tradeoffs, or deduced from issues such as data, analysis or symptoms. Rankings can be sorted by title, author, editions, style, level of difficulty, citations, prerequisites, mathematics, and so on.

The present wiki includes pages for each title showing authors, publication date, category, tags, links to content, external links, possibly a book site, other media, and user comments. Sources usually have some combination of table of contents, glossary, index, notes, hyperlinks, bibliography, code and exercises. These may be in any of various formats, e.g. PDF, HTML, hardcover, paperback, flash or e-reader. External pages or bookmarks may provide a booklist linked to the wiki pages. There may also exist other reviews or a synopsis. Authors have biographies, publications, blogs, organizations, teams, social networks and feeds. Tools have sources, possibly open-source, vendors, costs, and dependencies or chains. Projects can be active or archive.

New wiki pages include Guernsey 2009 on databases, Ogrinz 2009 on enterprise mashups, Resig 2006 on javascript, and Newkirk 2004 on test-driven development (TDD).

Image: TIS topic list


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: