wireframes for author-user-link #60

rija · 2018-01-21T05:56:54Z

No description provided.

user story and acceptance test scenarios drafted

updated the main feature context class to distinguish betwewen admin login and regular user login. as we need to log as either in turn in the course of the scenarios for this feature set.

… state for automated tests different features need different type of tests data and tests user, so the set up of the initial state need be able to configured differently for each feature. The bare minimul is kept as a before suite hook on the main context, but the rest will be done in a Background scenario so I wrote the appropriate step definitions and update the feature files accordingly.

started writing test scenario for issue #60 for showing a user's datasets on his/her profile once he/she has been linked to an author. So far acceptance criteria drafted and started implementing steps definitions.

…ts using sql In order to tests that a user can have datasets of author is attached to displayed on his/her profile, we make it possible to create a new user that can sign in from the scenarios. This is because the default users in test data already have the same tests datasets listed on their profile because they submitted them. we want a user with no existing link to datasets prior to running the tests

…ss more than one authors It's possible that a user has authored datasets under multiple name so it should be possible to attach more than one author to a user and therefore the user profile should show all datasets of all attached authors.

… user on his/her profile followed same design pattern as for "Your submitted datasets" section.

…he user appears for each dataset add additional query to enable showing under which author name the user has authored a dataset in the table listing his/her datasets. This fixes #60

…ne author. Removed scenario for displaying two authors' dataset on user profile.on issue #60 feature Added scenario to prevent a user to be associated to more than one author on issue #56 feature Created a Given step for setting a author/user link in the database for the issue #56 feature in AuthorUserContext.php and reused it in the iAmLinkedToAuthor given step for issue #60 in DatasetsOnProfileContext.php

In order to simplify and speed up Behat automated tests, we will connect to the postgresql sever in the vagrant box directly from the php code. connecting the dev environment to postrgresql inside vagrant box is 3-steps: setting port forwarding in Vagrantfile is only first step. Secondly, we need to changes posgresql.conf to get the database server to listen on all interface, not just loopback interface. Thirdly we need to add client authorisation for the dev environment in pg_hba.conf In this commit, I've updated default attributes in Chef to allow just that. Note that the 10.0.2.2 IP address used in client_auth is a Vagrant "magic" IP address that represent the host running the Vagrant box.

Switch to direct database connection from the test's PHP code instead of 3 layers of indirections.

the step to load a user into the database nows connect to the postgresql database server in the vagrant box directly from PHP. Also the sql has been updated into a insert query that can be used in pg_* php functions instead of a PGSQL command. a private function actually handles the database loading of a user for cases when we want to do it without wanting to set the user_login/password.

…or clarity, speed and robustness whenever it's possible, the php code of the tests connect directly to the database server in the vagrant box. Only step functions that manipulate database dump cannot do that and need to go thtrough exec - vagrant - ssh - pg_restore/pgsql- file indirection Terminating backend is less brittle: if it precede a database drop command, we ensure no new connection can be made between termination and database drop Also the occasional CDbConnection error "FATAL: terminating connection due to administrator command server closed the connection unexpectedly" has been fixed by restarted the php-fpm daemon after terminating database backends. The above error having been fix, I can now remove the calls to "sleep" peppered across the automated tests codebase that was remediating it Added consistency across features, on how user record needed by the tests are loaded Removed sql file used to hold command to pass on to the exec - vagrant - ssh - pg_restore/pgsql- file indirection only keep sql files for a user record and for database schema and original test data. DRY the code by calling a step from another one in gigadbWebSiteIsLoadedWithProducitonLikeData() step defintion

…m the work done on branch for issue #56 and #60 directly connect to postgresql database from php code.

Now that the #56, #60 branch has been rebased into the #57 branch I can test for the gigadb user id to show up in the author view after an admin validate a dataset claim.

… dataset table