You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is phrased as "as a developer" because this is a technology proof of concept - we want to be able to show that we can add or update an acknowledgement and have it affect the layout of the graph
I'm going to put all the details into the A/C here but really its more of an epic than a simple user story.. we should create a separate branch for this.
Acceptance criteria - graph layout
When I go to the people tab I can click a button to see the graph view
In the graph view I see all the people in the current db (for now just show all)
Each person appears with a circle and their bio pic in the photo
If there is an acknowledgement between two people there is a line added between those two people
The graph of people and edges has a workable auto-layout - such as in the vis.js sample already used
Acceptance criteria - scaling test
As an admin its possible to press a button in the admin portal to add some fake users (10 at a time)
As an admin its possible to press a button in the admin portal to add fake acknowledgements between any existing users (n at a time)
As an admin it's possible to remove all fake users and fake acknowledgements (or failing that you can just drop table)
The script adds about 30 users and 50 edges or so
The graph layout works OK at that scale
Commentary: As an interesting excerize it would be interesting to see what happens when we have hundreds of users and when it starts to 'not work' any more.
The text was updated successfully, but these errors were encountered:
This is phrased as "as a developer" because this is a technology proof of concept - we want to be able to show that we can add or update an acknowledgement and have it affect the layout of the graph
I'm going to put all the details into the A/C here but really its more of an epic than a simple user story.. we should create a separate branch for this.
Acceptance criteria - graph layout
Acceptance criteria - scaling test
Commentary: As an interesting excerize it would be interesting to see what happens when we have hundreds of users and when it starts to 'not work' any more.
The text was updated successfully, but these errors were encountered: