Merge pull request #26 from GovReady/headless_titlecon

Fix title inconsistencies. Added docs about setting headless mode on/…

source/appendixes/version-notes/migration-guide-for-govready-q-v0-8-6-to-v0-9-x.rst

@@ -54,25 +54,25 @@ Migration Process
 -----------------
 
 General Guidelines
-^^^^^^^^^^^^^^^^^^
+''''''''''''''''''''''''''''''
 
 * Make sure your live data is backed up, and can be found and restored properly, before, during, and after the migration.
 * Do test migrations on test servers first, to ensure you understand the process and have worked out any kinks, before working on production servers.
 * Check for customizations, and preserve or modify them as needed.
 
 Back Up Your Production Data
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+''''''''''''''''''''''''''''''
 
 * Ensure that you have a backup of your production data, and that it is safe, and will be available for a successful restore.
 
 Read the Documentation
-^^^^^^^^^^^^^^^^^^^^^^
+''''''''''''''''''''''''''
 
 * Familiarize yourself with the migration process before conducting the first test migration.
 * Make sure GovReady-Q official documentation is working for you.
 
 Do a Test Migration
-^^^^^^^^^^^^^^^^^^^
+'''''''''''''''''''''''''
 
 * Use test data that will model and exercise the same features as your production data.
 * Use a clean install of the version you run in production, with test data installed.
@@ -83,7 +83,7 @@ Do a Test Migration
 * Optionally have selected end-users sign into the upgraded test instance to perform their own tests.
 
 Distribute a Migration Plan
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+''''''''''''''''''''''''''''''
 
 * Create a migration plan. Include user impacts, timelines, contingency plans, and technical details (perhaps in a separate technical plan).
 * Confirm that your colleagues who are responsible, accountable, consulted, and informed about the migration are satisfied with the plan.

source/installation-and-setup/container-based-installation/advanced-container-config.rst

@@ -79,7 +79,7 @@ container, which will be destroyed when the container is destroyed.
 There are two methods for connecting to a persistent database.
 
 Sqlite file
-^^^^^^^^^^^
+'''''''''''''
 
 You can use a Sqlite file stored on the host machine:
 
@@ -106,7 +106,7 @@ Of course, do not do this if the host machine has a user 1000 that you
 do not trust.
 
 Remote database
-^^^^^^^^^^^^^^^
+''''''''''''''''''''
 
 You can also connect to a database running on a remote system accessible
 to the Docker container.

source/installation-and-setup/server-based-installation/linux/ubuntu/index.rst

@@ -216,7 +216,7 @@ The following should fail as the user will not have the right privileges.
 .. note::
    For Windows Subsystem for Linux (Ubuntu 20.04) you might get the error below. the default initsystem is not **systemd** which **systemctl** depends on (probably **Sysvinit**). To still achieve the same usage you have to change the syntax for this command from **systemctl start service_name** to	**service service_name start** (i.e. ``sudo service mysql status``)
 
-.. code:: bash
+.. code:: text
 
     system has not been booted with systemd as init system (PID 1). Can't operate.
     Failed to connect to bus: Host is down

source/testing-for-govready-q/automated-testing.rst

@@ -64,6 +64,26 @@ To produce a code coverage report, run the tests with `coverage`:
     coverage run --source='.' --branch manage.py test
     coverage report
 
+For Developers
+~~~~~~~~~~~~~~~~~~~~~
+
+If you want to run automated tests in visible mode you can set the parameter test_visible to false in ``local/environment.json`` otherwise it will run in headless.
+::
+
+   {
+      ...
+      "test_visible": false,
+      ...
+   }
+
+This is a boolean for the HEADLESS variable in ``siteapp/settings``(the main point for automated test settings) that is a control for adding or avoiding ``--headless`` as an argument in ChromeOptions.
+
+::
+
+   if HEADLESS:
+            options.add_argument('--headless')
+
+
 Selenium Troubleshooting
 ~~~~~~~~~~~~~~~~~~~~~~~~
 

source/user-guide/user-guide.rst

@@ -315,23 +315,23 @@ relevant information as possible. Incomplete or sparse answers may cause
 an organization to fail a compliance process.
 
 How to answer a GovReady Data Grid question type?
-----------------------
+----------------------------------------------------
 
 The GovReady Data Grid question type is used to collect complex information from users on a single questionnaire page. To answer a GovReady Data Grid question type, click the green plus "+" at the top right of the grid, enter relevant information, and then click on the lower green plus "+" to add that information to the grid. Users can add multiple rows by clicking the lower green plus "+" again. Click on the "next question" button to save answers.
 
 See Video Demonstration, `Here
 <https://vimeo.com/418917502>`_.
 
 How to answer a GovReady boilerplate template?
-----------------------
+-----------------------------------------------
 
 User content authors can create questions that generate pre-filled out to make navigating through a module's questions easier. This content will vary from organization to organization. A boilerplate template allows a user to accept the template as is, edit the template, or write original content.
 
 See Video Demonstration, `Here
 <https://vimeo.com/418916949>`_.
 
 How to use the GovReady Authoring Tool?
-------------------------
+----------------------------------------------
 
 GovReady offers an in-app authoring functionality that enables users with certain permissions to change content within GovReady questionnaires. To access the Authoring Tool, click on the pencil icon at the top right of the questionnaire page. The authoring tool window will open on the right side of the screen. From the interface, users can change content, question type, and other facets of the questionnaire. Click "save" to save the changes on the questionnaire.