Test Plan

[vkichline]

I would like to propose a Usability Test Plan for the Core2ez framework.
Objective: define a set of progressively complex applications, and implement them with Core2ez.
Review each exercise for what met expectation, what exceeded expectation, and what failed to meet expectations. Rinse and repeat.

Here is a first pass at defining a list of test apps. These are goal oriented rather than feature oriented; other tests are needed to delve deep into each feature set. This it to make sure the forest stays in view as we deal with the trees.

0. Hello World - Just neatly put some text on the screen in two or three places. Different fonts, styles. One can do this now.
1. Display IMU Data - have 3-6 labels and 3-6 display fields displaying rapidly changing data. Flicker free, easy to program.
2. Display/Set the RTC - Nice clock formatting and display; use buttons to set the time/date. Should look good, be easy.
3. Choose one of five: for example, select an MQTT broker from a list. Requires specialized selection controls.
4. 7 of 9 - Select seven of 9 choices (more than fit on the screen.) Requires complex input controls, like menus or radio buttons.
5. Multi-step setup operation - Pick an SSID, enter & save password, manage connections. Requires multiple screens.
6. Display scrollable instructions - Multi-page display of word wrapped text.
7. Weather Station - Perhaps a poor example because it's hard to make it global. Some real, network connected app, though.

Let's discuss and refine this list a bit. If it's ordered well, we could sequence development to enable one level after another.
Any other needs that come up a lot? We should review customer issues for pain points and ensure they're addressed if appropriate.