Skip to content
This repository
tree: ff452cc24f
Fetching contributors…

Cannot retrieve contributors at this time

file 85 lines (62 sloc) 2.989 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85
Pettswood More TODO

DO THE DEMO A HUNDRED TIMES, IMPROVING EACH TIME
 - Use PW to test-drive some problem domain
- Twitter
- UPT

What was good at Functional Exchange:
Dynamic data lookups - real-time code demo with very fast feedback
Visi - a great new idea, for a new type of computing (tablets)
Audience participation - everyone has opinions to put forward.
- A vote for the next feature?

Things to avoid:
Just boxes and lines - boring
Monotonous plugging of a website - there needs to be a sequence of interesting points to engage the audience


Make the Demo the same as the docs, and the What Is? Doc, and the getting started

5 Intro
5 Go through what is
10 Demos
10 Questions, requests for demos



Fix WYSIWYG editor so that it don't completely fuck up the xml-ness of the HTML
 - Removes end tag of <link>
 - adds unclosed <br> tags everywhere
 - -removes the doctype and starting <html> tags

Add a helpful xml-structure-error-displayer, so that it is easy to find and fix XML well-formedness errors

Things I wanted to fix:
Business users don't edit HTML -> informed WYSIWYG
Fixture is hard ->
Too much boilerplate fixture ->


Talks Structure:

  Things to fix: 1 2 3

Solution: a b c

Examples: x y z

Use this graphical key as in-slide breadcrumbs.


Concept:
A toolbox of highly-compatible libraries to enable real-time construction of executable specifications:
 - The core - an HTML-to-test parser and executer
 - Integrations with build tools (sbt, ant, Maven, ...)
 - A WYSIWYG spec editor for the business to use
 - Incorporates the automations and lessons learned from previous production systems (toggle between test and result, nested tables, mixing, none/null/empty concepts, …)
 - In-browser creation of tests from templates, and addition of tables supported by existing fixture, as well as new types of table.
 -

Rules of engagement:
 - The document must be well-formed XML. HTML5 is fine.
 -
 -
 -
 -


Bugs:
*Still needs an SbtIntegrationHook in the test sources for it to run ==> Have a settings class that doesn't suck (unlike sbt's) that is also the hook.
* Good old NPE when first looking for copy of css in target. Works second time around.

New features to add:
ONLINE - Move Pettswood tests to their own folder: src/pettswood/resources/
Improve Concepts, so that learning new ones requires less code. C.f. tryElse in DomainBridge
Host in sonatype
Jang in toggler at start of test
Improve the default CSS - make it look neater, more up-to-date. Explore fonts, colours, etc. The usual.
Find a way to get HTML displayed out of github - extract the project to agmen-smith.co.uk and host it from there?
Simplify the "What is" doc.
Fill in Getting Started.doc
----- Begin Marketing -----
(Automatically) update the documentation snippets - an sbt plugin?
Sbt task to create template tests & Jang in wizzywig at start of test
Test different failure modes (e.g. no file, badly formed table, etc) and check there are appropriate error messages
Something went wrong with that request. Please try again.