mirror of
https://github.com/Xevion/exercism.git
synced 2025-12-08 12:07:04 -06:00
80 lines
2.8 KiB
Markdown
80 lines
2.8 KiB
Markdown
# Allergies
|
|
|
|
Given a person's allergy score, determine whether or not they're allergic to a given item, and their full list of allergies.
|
|
|
|
An allergy test produces a single numeric score which contains the
|
|
information about all the allergies the person has (that they were
|
|
tested for).
|
|
|
|
The list of items (and their value) that were tested are:
|
|
|
|
* eggs (1)
|
|
* peanuts (2)
|
|
* shellfish (4)
|
|
* strawberries (8)
|
|
* tomatoes (16)
|
|
* chocolate (32)
|
|
* pollen (64)
|
|
* cats (128)
|
|
|
|
So if Tom is allergic to peanuts and chocolate, he gets a score of 34.
|
|
|
|
Now, given just that score of 34, your program should be able to say:
|
|
|
|
- Whether Tom is allergic to any one of those allergens listed above.
|
|
- All the allergens Tom is allergic to.
|
|
|
|
Note: a given score may include allergens **not** listed above (i.e.
|
|
allergens that score 256, 512, 1024, etc.). Your program should
|
|
ignore those components of the score. For example, if the allergy
|
|
score is 257, your program should only report the eggs (1) allergy.
|
|
|
|
## Exception messages
|
|
|
|
Sometimes it is necessary to raise an exception. When you do this, you should include a meaningful error message to
|
|
indicate what the source of the error is. This makes your code more readable and helps significantly with debugging. Not
|
|
every exercise will require you to raise an exception, but for those that do, the tests will only pass if you include
|
|
a message.
|
|
|
|
To raise a message with an exception, just write it as an argument to the exception type. For example, instead of
|
|
`raise Exception`, you should write:
|
|
|
|
```python
|
|
raise Exception("Meaningful message indicating the source of the error")
|
|
```
|
|
|
|
## Running the tests
|
|
|
|
To run the tests, run the appropriate command below ([why they are different](https://github.com/pytest-dev/pytest/issues/1629#issue-161422224)):
|
|
|
|
- Python 2.7: `py.test allergies_test.py`
|
|
- Python 3.4+: `pytest allergies_test.py`
|
|
|
|
Alternatively, you can tell Python to run the pytest module (allowing the same command to be used regardless of Python version):
|
|
`python -m pytest allergies_test.py`
|
|
|
|
### Common `pytest` options
|
|
|
|
- `-v` : enable verbose output
|
|
- `-x` : stop running tests on first failure
|
|
- `--ff` : run failures from previous test before running other test cases
|
|
|
|
For other options, see `python -m pytest -h`
|
|
|
|
## Submitting Exercises
|
|
|
|
Note that, when trying to submit an exercise, make sure the solution is in the `$EXERCISM_WORKSPACE/python/allergies` directory.
|
|
|
|
You can find your Exercism workspace by running `exercism debug` and looking for the line that starts with `Workspace`.
|
|
|
|
For more detailed information about running tests, code style and linting,
|
|
please see [Running the Tests](http://exercism.io/tracks/python/tests).
|
|
|
|
## Source
|
|
|
|
Jumpstart Lab Warm-up [http://jumpstartlab.com](http://jumpstartlab.com)
|
|
|
|
## Submitting Incomplete Solutions
|
|
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|