Unittesting views part 1

[Yu-jinKim]

• Have actual tool names for the metric scrolling menu
  • JSON to configure the name to display
  • additional cleaning step for posting data
• Unittesting views:
  • Dashboard:
    • GET | correct context data
    • POST | plot using scrolling menus
    • POST | plot using filter
    • POST | delete filter
    • POST | save filter
      • Plot:
    • GET | correct form to reach final render function
    • GET | empty form

root@29cb345eed2c:/app# python trendyqc/manage.py test trend_monitoring.tests
Found 37 test(s).
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
.....................................
----------------------------------------------------------------------
Ran 37 tests in 49.630s

OK
Destroying test database for alias 'default'...

---

This change is 

[pep8speaks]

Hello @Yu-jinKim! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file trendyqc/trend_monitoring/backend_utils/plot.py:

Line 187:80: E501 line too long (83 > 79 characters) Line 194:80: E501 line too long (81 > 79 characters) Line 311:80: E501 line too long (155 > 79 characters) Line 313:80: E501 line too long (155 > 79 characters) Line 314:80: E501 line too long (155 > 79 characters) Line 315:80: E501 line too long (155 > 79 characters) Line 316:80: E501 line too long (155 > 79 characters) Line 440:80: E501 line too long (90 > 79 characters)

• In the file trendyqc/trend_monitoring/views.py:

Line 320:80: E501 line too long (84 > 79 characters)

• In the file trendyqc/trendyqc/settings.py:

Line 70:80: E501 line too long (98 > 79 characters) Line 302:2: W292 no newline at end of file

Comment last updated at 2024-06-18 10:47:14 UTC