Skip to content
This repository has been archived by the owner on Jul 29, 2020. It is now read-only.

Adding testing instructions #109

Merged
merged 4 commits into from
Sep 28, 2016
Merged

Adding testing instructions #109

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b17fb3d
Adding testing instructions
mortonjt Sep 19, 2016
2859a12
Update README.rst
mortonjt Sep 19, 2016
c2946f3
Update README.rst
mortonjt Sep 20, 2016
6c80cd3
Update README.rst
mortonjt Sep 22, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,3 +36,21 @@ Initial default test login credentials are:

**Password:** password

Testing
-------

To run the webserver locally, first run the following commands to insert a user with administrative access::

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also add the SQL commands to select the right database.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

\c ag_test

INSERT INTO ag.labadmin_users (email, password) VALUES ('master', '$2a$10$2.6Y9HmBqUFmSvKCjWmBte70WF.zd3h4VqbhLMQK1xP67Aj3rei86');

INSERT INTO ag.labadmin_users_access (access_id, email) VALUES (7, 'master');

Then you should be able to login with the following credentials

**User:** master

**Password:** password

After executing our existing unit test suite, access level for the user 'test' will be reset to '', i.e. they won't be able to see most of the main menu items. Thus, adding a second user 'master' with admin privileges is quite useful.