<commit_before>.. _socorro-test-checklist-chapter:

======================
Socorro Test Checklist
======================

This is a high-level system-wide checklist for making sure Socorro is working
correctly in a specific environment. It's a helpful template for figuring out
what you need to change if you're pushing out a significant change.

**Note:** This is used infrequently, so if you're about to make a significant change,
you should go through the checklist to make sure the checklist is correct and
that everything is working as expected and fix anything that's wrong, THEN
make your change, then go through the checklist again.

Lonnen the bear says, "Only you can prevent production fires!"

Last updated: February 6th, 2018


How to use
==========

"Significant change" can mean any number of things, so this is just a template.
You should do the following:

1. Copy and paste the contents of this into a Google Doc, Etherpad, or
   whatever system you plan to use to keep track of status and outstanding
   issues.

2. Go through what you copy-and-pasted, remove things that don't make sense,
   and add additional things that are important. (Please uplift any changes
   via PR to this document that are interesting.)


Checklist
=========

::

    Migrations
    ==========

    Make sure we can run migrations

    * Django migrations

      Local dev environment:
<commit_msg>Add verify version step to system checklist<commit_after>.. _socorro-test-checklist-chapter:

======================
Socorro Test Checklist
======================

This is a high-level system-wide checklist for making sure Socorro is working
correctly in a specific environment. It's a helpful template for figuring out
what you need to change if you're pushing out a significant change.

**Note:** This is used infrequently, so if you're about to make a significant change,
you should go through the checklist to make sure the checklist is correct and
that everything is working as expected and fix anything that's wrong, THEN
make your change, then go through the checklist again.

Lonnen the bear says, "Only you can prevent production fires!"

Last updated: February 6th, 2018


How to use
==========

"Significant change" can mean any number of things, so this is just a template.
You should do the following:

1. Copy and paste the contents of this into a Google Doc, Etherpad, or
   whatever system you plan to use to keep track of status and outstanding
   issues.

2. Go through what you copy-and-pasted, remove things that don't make sense,
   and add additional things that are important. (Please uplift any changes
   via PR to this document that are interesting.)


Checklist
=========

::

    Verify version
    ==============

    Before doing anything, verify the environment(s) that you're testing
    are running the version you expect.

    * local dev: http://localhost:8000/api/Status
    * -stage: https://crash-stats.allizom.org/api/Status
    * -prod: https://crash-stats.mozilla.com/api/Status


    Migrations
    ==========

    Make sure we can run migrations

    * Django migrations

      Local dev environment:

{'fraction_non_alphanumeric': 0.09777070063694268, 'fraction_numerical': 0.005732484076433121, 'mean_word_length': 3.9231974921630095, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4715573', 'n_tokens_mistral': 854, 'n_tokens_neox': 764, 'n_words': 428}