Commit eed46dd7 authored by Paul Slaughter's avatar Paul Slaughter

Add clause to fixing security issue message

parent 5e73c044
...@@ -108,6 +108,6 @@ original. ...@@ -108,6 +108,6 @@ original.
### Fixing Security Issues ### Fixing Security Issues
When refactoring old code, it's important that we don't accidentally remove specs written to catch security issues. When refactoring old code, it's important that we don't accidentally remove specs written to catch security issues which might still be relevant.
We should mark specs with `#security` in either the `describe` or `it` blocks to communicate to the engineer reading the code that by removing these specs could have severe consequences down the road, and you are removing code that could catch a reintroduction of a security issue. We should mark specs with `#security` in either the `describe` or `it` blocks to communicate to the engineer reading the code that by removing these specs could have severe consequences down the road, and you are removing code that could catch a reintroduction of a security issue.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment