Skip to content

Testing a dev branch on iPhone, Internet Explorer Windows, Android

Jump to bottom
John Carroll edited this page Oct 4, 2019 · 7 revisions

To test a development branch on iPhone, Windows/Internet Explorer, Android or any other browser/device combination unavailable on your Mac, you can either: 1) Point your device/browser to your development server or 2) Deploy branch to feature space and test there.

1) Point your device/browser to your development server:

  • Checkout the branch you want to test.
  • Temporarily add ALLOWED_HOSTS = ['*'] to fec/fec/settings/dev.py
  • Switch to a Wi-Fi network (that isn't the internal network).
  • ./manage.py runserver 0.0.0.0:8000
  • Get the IP address of your dev server with the following steps:
    • Go to System Preferences > Network
    • Choose the Wi-Fi network on the left
    • Click Advanced… in the lower right
    • Choose TCP/IP tab. The IPv4 Address is your dev server's IP.
  • Make sure your test and development device(Mac) are on the same WIFI network.
  • Visit the IP address at port :8000 on the device/browser.

Note: Remove ALLOWED_HOSTS from dev.py before committing/pushing any changes.

2) Deploy to feature

Another alternative is to push a test version of this branch to the feature space and visit it on the device/browser you want to test.

  • BEFORE PUSHING TO FEATURE SPACE, send a message in Slack to @here, to make sure someone else does not have something already deployed to the feature space that they are currently using for testing.
  • Create a test copy of the branch you want to test
  • Open /tasks.py and find the line below.
#('feature', lambda _, branch: branch == 'feature/3016-pre-election-reporting-dates-tables-template'),

  • Un-comment this line and put your test branch name in single quotes after branch == :

  • commit your change of tasks.py

  • git push -u origin [your test branch name]

    • (You could alternatively edit tasks.py directly on your PR branch an push that to feature, just be sure to revert tasks.py after deploying to feature, so it does not get tracked as a changed file in your PR.)

  • Wait for CircleCI to complete the build successfully .

  • Visit https://fec-feature-cms.app.cloud.gov/ on the device/browser combination you want to test.

**Note:** Internet Explorer 11 may behave differently depending on the devices Windows build-pack and other configurations, so it is important to test several different devices. For example, the configuration of FEC-issued MS Surface tablets has shown to have IE 11 issues that other Windows 7/10 environments might not.
Clone this wiki locally