Page Comparison

...

vagrant@vagrant:~$ sudo /edx/bin/supervisorctl status
analytics_api                    RUNNING   pid 2050, uptime 0:15:35
certs                            RUNNING   pid 8656, uptime 0:00:02
ecommerce                        RUNNING   pid 2084, uptime 0:15:35
ecomworker                       RUNNING   pid 2045, uptime 0:15:35
edxapp:cms                       RUNNING   pid 2083, uptime 0:15:35
edxapp:lms                       RUNNING   pid 2079, uptime 0:15:35
edxapp_worker:cms_default_1      RUNNING   pid 2099, uptime 0:15:34
edxapp_worker:cms_high_1         RUNNING   pid 2095, uptime 0:15:34
edxapp_worker:cms_low_1          RUNNING   pid 2086, uptime 0:15:34
edxapp_worker:lms_default_1      RUNNING   pid 2096, uptime 0:15:34
edxapp_worker:lms_high_1         RUNNING   pid 2101, uptime 0:15:34
edxapp_worker:lms_high_mem_1     RUNNING   pid 2090, uptime 0:15:34
edxapp_worker:lms_low_1          RUNNING   pid 2100, uptime 0:15:34
forum                            RUNNING   pid 2046, uptime 0:15:35
insights                         RUNNING   pid 2104, uptime 0:15:34
notifier-celery-workers          RUNNING   pid 2049, uptime 0:15:35
notifier-scheduler               RUNNING   pid 2059, uptime 0:15:35
programs                         RUNNING   pid 2048, uptime 0:15:35
xqueue                           RUNNING   pid 2065, uptime 0:15:35
xqueue_consumer                  RUNNING   pid 2044, uptime 0:15:35
vagrant@vagrant:~$

E-Commerce Test

NOTE: These changes are currently in a pull request.

1. Make sure FEATURES.ENABLE_OAUTH2_PROVIDER is set to true.
2. Follow the Configure the LMS section of Test Your E-Commerce Application steps 1–9, see setting changes below. Skip the step for starting the app server, since it's already started.
3. Follow the Configure E-Commerce section of Test Your E-Commerce Application steps 1–8, see setting changes below. Instead of starting the app server, reboot the server before trying to access E-Commerce so the settings can take effect.

...

1. Set up the bok-choy test server. This will take about 15 minutes.

   paver test_bokchoy -r

   -r stands for --serversonly.

2. In another terminal window, run tests. The test modules are relative to common/test/acceptance/tests/.

   paver test_bokchoy -a -o -t video/test_video_events.py

   paver test_bokchoy -a -o -t video/test_studio_video_editor.py

   paver test_bokchoy -a -o -t lms/test_lms_cohorted_courseware_search.py

   -a stands for --fasttest and -o stands for --testsonly. Both options must be set while in client mode.

3. In another terminal window, run tests. The test modules are relative to common/test/acceptance/tests/.

   paver test_bokchoy -a -o -t lms/test_problem_types.py

   There are known failures for this test suite currently.

4. Make sure X11 forwarding work. You must be on the host machine (physically or via Screen Sharing). X11 forwarding doesn't work if you're SSHed into the host machine.

   1. Install XQuartz

   brew cask install xquartz

   2. Let Vagrant know you want to forward X11.

   export VAGRANT_X11=1

   3. Start the guest box and SSH into it.

   vagrant up && vagrant ssh

   4. Verify X11 forwarding is working in the guest VM.

   $ echo $DISPLAY

   localhost:10.0

   You can also start Firefox, for example, and it should show up on your desktop via XQuartz.

   firefox

E-Commerce Test

...

1. Follow the Configure the LMS section of Test Your E-Commerce Application steps 1–9.
2. Follow the Configure E-Commerce section of Test Your E-Commerce Application steps 1–8.

...