METADATA 5.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140
  1. Metadata-Version: 2.1
  2. Name: allure-python-commons
  3. Version: 2.13.5
  4. Summary: ('Contains the API for end users as well as helper functions and classes to build Allure adapters for Python test frameworks',)
  5. Home-page: https://allurereport.org/
  6. Author: Qameta Software Inc., Stanislav Seliverstov
  7. Author-email: sseliverstov@qameta.io
  8. License: Apache-2.0
  9. Project-URL: Source, https://github.com/allure-framework/allure-python
  10. Keywords: allure reporting report-engine
  11. Classifier: Development Status :: 5 - Production/Stable
  12. Classifier: Intended Audience :: Developers
  13. Classifier: License :: OSI Approved :: Apache Software License
  14. Classifier: Topic :: Software Development :: Quality Assurance
  15. Classifier: Topic :: Software Development :: Testing
  16. Classifier: Programming Language :: Python :: 3
  17. Classifier: Programming Language :: Python :: 3 :: Only
  18. Classifier: Programming Language :: Python :: 3.7
  19. Classifier: Programming Language :: Python :: 3.8
  20. Classifier: Programming Language :: Python :: 3.9
  21. Classifier: Programming Language :: Python :: 3.10
  22. Classifier: Programming Language :: Python :: 3.11
  23. Classifier: Programming Language :: Python :: 3.12
  24. Requires-Python: >=3.6
  25. Description-Content-Type: text/markdown
  26. Requires-Dist: attrs >=16.0.0
  27. Requires-Dist: pluggy >=0.4.0
  28. ## Allure Common API
  29. [![Release Status](https://img.shields.io/pypi/v/allure-python-commons)](https://pypi.python.org/pypi/allure-python-commons)
  30. [![Downloads](https://img.shields.io/pypi/dm/allure-python-commons)](https://pypi.python.org/pypi/allure-python-commons)
  31. > The package contains classes and functions for users of Allure Report. It can
  32. > be used to enhance reports using an existing Allure adapter or to create new
  33. > adapters.
  34. [<img src="https://allurereport.org/public/img/allure-report.svg" height="85px" alt="Allure Report logo" align="right" />](https://allurereport.org "Allure Report")
  35. - Learn more about Allure Report at [https://allurereport.org](https://allurereport.org)
  36. - 📚 [Documentation](https://allurereport.org/docs/) – discover official documentation for Allure Report
  37. - ❓ [Questions and Support](https://github.com/orgs/allure-framework/discussions/categories/questions-support) – get help from the team and community
  38. - 📢 [Official announcements](https://github.com/orgs/allure-framework/discussions/categories/announcements) – stay updated with our latest news and updates
  39. - 💬 [General Discussion](https://github.com/orgs/allure-framework/discussions/categories/general-discussion) – engage in casual conversations, share insights and ideas with the community
  40. - 🖥️ [Live Demo](https://demo.allurereport.org/) — explore a live example of Allure Report in action
  41. ---
  42. ## User's API
  43. Install an adapter that suits your test framework. You can then add more
  44. information to the report by using functions from the `allure` module.
  45. ### Decorators API
  46. Use these functions as decorators of your own functions, e.g.:
  47. ```python
  48. import allure
  49. @allure.title("My test")
  50. def test_fn():
  51. pass
  52. ```
  53. The full list of decorators:
  54. - `allure.title`
  55. - `allure.description`
  56. - `allure.description_html`
  57. - `allure.label`
  58. - `allure.severity`
  59. - `allure.epic`
  60. - `allure.feature`
  61. - `allure.story`
  62. - `allure.suite`
  63. - `allure.parent_suite`
  64. - `allure.sub_suite`
  65. - `allure.tag`
  66. - `allure.id`
  67. - `allure.manual`
  68. - `allure.link`
  69. - `allure.issue`
  70. - `allure.testcase`
  71. - `allure.step`
  72. Refer to the adapter's documentation for the information about what decorators
  73. are supported and what functions they can be applied to.
  74. ### Runtime API
  75. Most of the functions of Runtime API can be accessed via `allure.dynamic.*`.
  76. Call them at runtime from your code.
  77. The full list includes:
  78. - `allure.dynamic.title`
  79. - `allure.dynamic.description`
  80. - `allure.dynamic.description_html`
  81. - `allure.dynamic.label`
  82. - `allure.dynamic.severity`
  83. - `allure.dynamic.epic`
  84. - `allure.dynamic.feature`
  85. - `allure.dynamic.story`
  86. - `allure.dynamic.suite`
  87. - `allure.dynamic.parent_suite`
  88. - `allure.dynamic.sub_suite`
  89. - `allure.dynamic.tag`
  90. - `allure.dynamic.id`
  91. - `allure.dynamic.manual`
  92. - `allure.dynamic.link`
  93. - `allure.dynamic.issue`
  94. - `allure.dynamic.testcase`
  95. - `allure.dynamic.parameter`
  96. - `allure.attach`
  97. - `allure.attach.file`
  98. - `allure.step`
  99. Refer to the adapter's documentation for the information about what functions
  100. are supported and where you can use them.
  101. ## Adapter API
  102. You may use `allure-pytest-commons` to build your own Allure adapter. The key
  103. elements of the corresponding API are:
  104. - `allure_python_commons.model2`: the object model of Allure Report.
  105. - `allure_python_commons.logger`: classes that are used to emit Allure Report objects (tests, containers, attachments):
  106. - `AllureFileLogger`: emits to the file system.
  107. - `AllureMemoryLogger`: collects the objects in memory. Useful for
  108. testing.
  109. - `allure_python_commons.lifecycle.AllureLifecycle`: an implementation of
  110. Allure lifecycle that doesn't isolate the state between threads.
  111. - `allure_python_commons.reporter.AllureReporter`: an implementation of
  112. Allure lifecycle that supports some multithreaded scenarios.
  113. A new version of the API is likely to be released in the future as we need
  114. a decent support for multithreaded and async-based concurrency (see
  115. [here](https://github.com/allure-framework/allure-python/issues/697) and
  116. [here](https://github.com/allure-framework/allure-python/issues/720)).