Posted by cadsmith on May 9, 2009
Tools evolve and drive inventors to new efforts. The wiki is probably no exception. It can be used to comment software and track bugs. Static content pages can be translated to wiki format using automated keyword hyperlinking and tagging. It seems to be the case that, by adding a few simple additional field types, they can be made more active. For example, a selector entry might be switched between values to use different other pages. So we enter the world of wiki-based computing. Documentation applications handle system descriptions, designs, metadata and statistics. It is not impossible for them to add operation and debugging. Each page is a memory snapshot or state of a set of values which can include hyperlinks and tags. A series of these can be used to drive activity just as a set of source code modules can be an instance of an algorithm, or machine components can be an engine. These modules are versioned and there can be a selector field parameter to string the correct choices together. This gives some flexibility in either pre-specifying order of execution, or allowing a test-driven approach to exercise combinations until a result is obtained. Automated editing or refactoring is more complex; this can be content-driven or result-driven. It may be possible for the wiki to edit itself to adapt to some external context or usage. A processing medium would have the ability to execute from wiki description or code to binary. This implies a ware descriptor language. Applications might be imagined for emulation, virtualization or hypervisors. This allows digital experiments to compare implementations prior to production. A wiki can also then become an operational component of a system. Pieces may be upgraded to other media or machines. Consider the wiki OS, model, processor, grid, and infrastructure. These are based on a built-in CMS, alerts, activities, artifacts, and abstractions. Analyzer output can generate wiki pages which may also be used as input to resume from. Dimensions of page relationships include hyperlinks, timestamp, writer, as well as content matches under search patterns, and other rules. Set the clock and see what establishes domains for the entry title.
Recent reading list Barrett 2008 on mediawiki, Ford 2008 enterprise s/w, Souders 2007 performance, Hamill 2004 unit testing, Crispin 2002 extreme programming, and Peck 2009 on Gimp.
New socnet test activity started on Daney’s SaRnet.
Posted in Uncategorized | Tagged: books, documentation, enterprise, performance, test, wiki | Leave a Comment »
Posted by cadsmith on November 30, 2008
Tiddlywiki has an html file that can be installed on local storage as a wiki app. The snapshot shown above is from a laptop instance; another was created on a flash drive which allows portability between devices. Google chrome was not able to save edits. Flock seemed to work okay.
Posted in Uncategorized | Tagged: flock, tiddlywiki, wiki | 2 Comments »
Posted by cadsmith on November 24, 2008
There is a common logic behind various website designs such as Google, Amazon and Imdb. The goals are to achieve clarity and make the user’s life easier. Navigation and search are key. They reinforce the user’s ability to quckly get the idea and complete the task. The site ID, home page, search, sections and utilities are easily found. This is the thesis of Don’t Make Me Think, Krug, 2005, a popular book about empirical web usability testing. Wikis are another aspect of this quickness approach. Also see author’s site and additional resources.
Posted in Uncategorized | Tagged: amazon, books, google, imdb, test, usability, wiki | Leave a Comment »
Posted by cadsmith on November 19, 2008
In previous posts, we have looked at feeds as updates for resources and commentary. It can also be useful to convert their current contents into a web page. For example, links can be inserted into a wiki by pasting from rss2html sourced from a bookmark site such as delicious using selected tags. This is the case for The Art of Debugging with GDB, DDD and Eclipse, Matloff and Salzman, 2008 based on gdb tag, and Lab Notebook from notebook tag. The wiki itself supplies another feed. It is possible then to translate between content management system (CMS) types such as bookmarks, wiki, database, spreadsheet, documentation or website.
Posted in Uncategorized | Tagged: books, CMS, Del.icio.us, gdb, notebook, RSS, rss2html, web2.0, wiki, youtest | Leave a Comment »
Posted by cadsmith on July 13, 2008
Edited smartpen wiki for activities.
Read JUnit in Action, Massol and Husted, 2003. Wiki.
Posted in Uncategorized | Tagged: books, livescribe, wiki | Leave a Comment »
Posted by cadsmith on February 22, 2008
“Game Testing All in One”, Schultz & others, 2005, 511pp describes how software testing techniques can be applied to games. After a humorous introduction orients the reader to the differences between gamer and tester approaches (e.g. rules 1 & 2 taken from Hitchhiker’s Guide, & X-Files or Ice-Nine, respectively), the authors reveal their knowledge of some popular titles as well as methods for improving the user’s experience. Book chapters have exercises answered in appendices. The contents demonstrate how to dissect a game for testing, and drive the software and hardware components in both well-defined and ad-hoc fashions. Testers get to know the games inside out and often spend weeks working through the various phases until release. Beta, online and multiplayer testing are also covered. Automation tools are used (since the game AI usually isn’t responsible for the testing part, too). Document, form and test flow diagram templates are detailed in an appendix. There are links to some commercial and public-domain tools to support the effort, e.g. documentation in a wiki.
Testing of mobile devices is covered in a recent webcast. Equipment costs can be lowered using combined analyzer and generator components local to a test station or connected using web-enabled LXI and IEEE 1588 timing.
Posted in Uncategorized | Tagged: books, games, test, wiki | Leave a Comment »