CFMTech/pytest-monitor

Issues

• Add postgres DB handler

  #77 opened a year ago by Veritogen
  1

• Missing metrics for failed tests

  #65 opened 2 years ago by husmen
  9

• --no-monitor breaks pytest.raises and django_assert_num_queries

  #79 opened 8 months ago by Veritogen
  2

• Add Bitbucket CI details to

  #75 opened a year ago by Veritogen
  0

• Use black and flake8 with pre-commit hooks

  #72 opened a year ago by js-dieu
  0

• Drop python 3.7/pytest 5.*

  #67 opened 2 years ago by js-dieu
  0

• Support for newer python versions

  #64 opened 2 years ago by twmr
  1

• Running pytest after install pytest-monitor results in `FileNotFoundError: [Errno 2] No such file or directory (originated from sysctl(HW_CPU_FREQ))`

  #58 opened 2 years ago by justinxzhao
  6

• NotImplementedError: can't find current frequency file

  #60 opened 2 years ago by Lucas-C
  4

• Write monitor-output of tests to console

  #46 opened 3 years ago by danielhuppmann
  6

• Crash on __init__ if psutil.cpu_freq() gives no results

  #56 opened 3 years ago by MattiasMartens
  1

• add support for unittests (via pytest)

  #39 opened 4 years ago by stas00
  9

• unicode issue in determine_scm_revision with Perforce

  #54 opened 3 years ago by jdhalimi
  0

• Incorrect result

  #48 opened 3 years ago by eldar-mustafayev
  6

• creating/binding a socket in a fixture causes it to not close

  #53 opened 3 years ago by altendky
  6

• pytest.skip() in a fixture causes an AttributeError for monitor_results during teardown

  #50 opened 3 years ago by altendky
  5

• Backend realization

  #42 opened 3 years ago by dremdem
  2

• Provide an option to force garbage collector to run between tests

  #40 opened 3 years ago by js-dieu
  2

• Unable to send measures on monitor-server

  #43 opened 3 years ago by js-dieu
  0

• discuss best memory measurement approach and possible leak detection

  #41 opened 4 years ago by stas00
  0

• Using sqlite's JSON field to store JSON data instead of text.

  #24 opened 4 years ago by js-dieu
  0

• Module with Doctests item fail to run even with --no-monitor option.

  #35 opened 4 years ago by js-dieu
  0

• Got `AttributeError` when start `pytest` session

  #23 opened 4 years ago by DKorytkin
  4

• argparse.ArgumentError: argument --remote: conflicting option string: --remote on start testing session

  #31 opened 4 years ago by SI7-Agent
  6

• Add Test Status Information

  #27 opened 4 years ago by Pyxtraker
  0

• Automatic gathering of a CI build information

  #25 opened 4 years ago by js-dieu
  0

• Monitor usage resulting in repeated printing

  #26 opened 4 years ago by csheaff
  7

• Use json format to describe a session

  #21 opened 5 years ago by js-dieu
  0

• Provide a specification of the API for remote use

  #15 opened 5 years ago by js-dieu
  0

• Use http code from standard http package

  #19 opened 5 years ago by js-dieu
  0

• No execution contexts get pushed when using a remote server

  #12 opened 5 years ago by js-dieu
  0

• A local database is always created, even with --no-db option

  #14 opened 5 years ago by js-dieu
  0

• Change default analysis scope from function+module to function

  #13 opened 5 years ago by js-dieu
  0

• Unable to send metrics to remote server

  #9 opened 5 years ago by js-dieu
  0

• Ability to add a tag/description to a run

  #4 opened 5 years ago by js-dieu
  0

• Change item name to follow the python object naming convention

  #5 opened 5 years ago by js-dieu
  0

• Provide times using a differential aproach instead of absolute one

  #3 opened 5 years ago by js-dieu
  0

• pytest-monitor does not return when explicitely skipping a test

  #2 opened 5 years ago by js-dieu
  0

• Collect child processes metrics

  #1 opened 5 years ago by s0undt3ch
  4