Scenario/user-testing
List of features and flows that are based on assumptions and need to be tested.
Scenario input
Starting point: users know the process, we assist and give pointers on how to use their existing process in GN. The user has the editor role.
Question: how do you work now
Observing: does this work in GN
Nudging: suggest a better way or workaround for missing features
Not in scope of testing:
login, user rights > not available in test environment
Priorities in testing:
besluittype plugin (needs to be fixed before testing)
global text editing
RDFA tags and placement of text in the correct tags (related to templates)
sjabloon
citatenplugin (detect issues)
public/not public
signing
publishing
"melden"
Nice to haves:
printing
User testing
General flow: preparing a meeting
Is the meeting page/structure understood
Is the concept agendapoints understood
Can they fill out the general meeting info?
Can they add agendapoints
Can they add attendees
Can they prepare a "besluit"
Can they vote a "besluit"
Is public/not public understood?
Can they publish a meeting
Is signing a section understood?
Publish an agenda
Publish an excerpt
Publish the notulen
Editor fuctions
Entering/editing text: typing, delete, backspace > where are the issues?
Plugins/templates > is it clear what they do?
Text styling: how much is this used?
Lists: how is this used? What are the limitations?
RDFA: how is this understood? Is it clear what is behind the text input?
RDFA: is text put correctly in the RDFA tags.
Copy/paste: are there a lot of issues? Is this working? Which software are the using to copy/paste
Citaten > see next point
Citatenplugin:
How many citaten does a user want to add at the same time?
Can they find the correct article?
Does the keyword trigger work? Do they know what to type?
Printing
Which pages do they want to print?
How do they print them? Do they need a print button?
Last updated