allure-framework / allure-framework/allure-python
allure plugin for robotframework-seleniumlibrary
- Langage dominant
- Python
- Étoiles
- 814
- Forks
- 260
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)
#### I'm submitting a ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
This could be an good example or part of a robot adapter
```python
import allure
from SeleniumLibrary import ScreenshotKeywords
from SeleniumLibrary.base import keyword, LibraryComponent
class AllureSeleniumPlugin(LibraryComponent):
@keyword
def capture_page_screenshot(self, filename='selenium-screenshot-{index}.png'):
path = ScreenshotKeywords(ctx=self.ctx).capture_page_screenshot(filename)
allure.attach.file(path, attachment_type=allure.attachment_type.PNG)
```
```robot
Library SeleniumLibrary plugins=AllureSeleniumPlugin
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par l’exemple Python AllureSeleniumPlugin proposé et son point d’entrée capture_page_screenshot. Vérifiez comment le paramètre de Robot Framework Library transmet plugins=AllureSeleniumPlugin, puis déterminez la portée requise de l’intégration. Done doit fournir un plugin SeleniumLibrary utilisable qui joint les captures d’écran de page capturées aux rapports Allure.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- testing
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100