VIVO-1904: Test VIVO functionality from pre to post sprint i18n branches

[chenejac]

Don Elsborg (Migrated from VIVO-1904) said:

Test VIVO functionality for a VIVO 1.11 instance which has some data and it's behavior following a i18n upgrade.

This test will not include any of the language functionality. It's purpose is for VIVO sites which aren't concerned with languages and only want to stay current with VIVO.

 

Environment:

VIVO/Vitro built from master branches using SDB.

Setup is using VIVO-docker2

Will create a simple set of data in the GUI for:

Person, Department, person position in department

 

Next will remove the VIVO docker image, rebuild the image using the sprint-i18n branch.

Observe what the data looks like.

Run additional tests

[chenejac]

Don Elsborg said:

Per work with team.

I validated that the person, position, and department are visible post i18n branch build.

Validated the sha on the GUI as: 48acad0 which correlates to: [https://github.com/vivo-project/VIVO/commit/48acad04d123e76677e53709fcec4c228168867b]

 

So this implies that existing data pre-i18n without language support will most likely be unaffected. Note that I didn't test using named graphs for data.

 

[chenejac]

Don Elsborg said:

Per zoom call, test the following in order to see how behavior changes for potential firsttime/everytime issues.

Change the following in the GUI and observe: class group name class group display rank class assignment to class group class display name class display rank object property display name object property class group object property display rank

[chenejac]

Benjamin Gross said:

If it wasn't obvious, the test process should be to change the things above in the GUI, observe the change, then restart the application and observe if the change remains.

[chenejac]

Ralph O'Flinn said:

will be wrapping up my run through of this later today