Session Tester Client Release 0.3

UI Changes: 

• application defaults to main editing screen. Start new session is a popup.
• embed JEdit Syntax text editor
• session document tree view: test session browser
• custom configuration for user-defined links to tools, cheatsheets resources, scripts, etc
• view/edit sessions, WYSISWYG and XML views

HTML Report rework:

• file structure
• look and feel
• smooth out workflow

Session Tester Application

- a more generalized tool for entering, editing and viewing session data, rather than just a tool for capturing session data
- since we are competing with text editors, we want to have a very basic IDE tool

General Session Tester Client Ideas

 Provide a client that provides more exploratory testing features than a text editor. This will be an IDE/workbench for exploratory testers.

Must be cross-platform. Support for Windows, Mac OS X and Linux.
Must have minimal dependencies, so that installations are simple. This is another reason not to have the client version depend on a database.

• full-fledged text editor with tag intellisense
• data collection, viewing and editing (in XML)
• session document tree view/organizational model
• timer with reminders to help focus
• idea primer - idea provocation
• cheatsheets, checklists, with ability to wire in your own
• tools/scripts - ability to wire in links to launch testing tools like Perlclip, or launch your bash/Ruby/Python et al test scripts
• custom session configuration (use charter instead of misson, etc.)
• open-ended timer for non SBT tasks

Philosophical goals:

• a flexible tool to help people get things done.
• document-based programming influence.  Mathematica interactive document model is powerful:
  •  http://www.youtube.com/watch?v=2g67M3NHL6A
  • see Scriba - site seems to be down, read this description: http://java.itags.org/java-programming/257788/
  •  

Technical: document persistence model with XML and XQuery (http://www.w3.org/XML/Query/ ) .

Avoid an RBDMS database model since it adds installation overhead for users, and XML documents can be used as artifacts

• maybe we could one day present here: http://nosqleurope.com/#describe

Once it is usable and has uptake, we'll move to the client/server model.

 Session Tester Team Version

 Group Session/Charter Management

• leads or managers create and distribute missions (empty session sheets to be filled in by testers)
• can map charters/sessions for team members to coverage models/projects, etc
  

 Session Tester Management Server

Reporting

• overview
• metrics
• reports to regulatory bodies
•  

Probably using a webserver of some sort.