Metadata-Version: 2.1
Name: testsinyaml
Version: 0.1.0
Summary: testsinyaml: Define your test cases in YAML and they will get executed and the result will be shared. 
Home-page: https://github.com/chowmean/testsinyaml
Author: chowmean
Author-email: gaurav.dev.iiitm@gmail.com
License: Apache-2.0
Description: # Tests In Yaml [testsinyaml]
        
        #### Define your test cases in yaml and they will get executed and result will be shared. 
        
        ### Installation
        ```
        pip install testsinyaml
        ```
        
        ### Usage:
        
        ```
        from testsinyaml import tests
        tests.execute(tests.yaml)
        ```
        How your tests.yaml should look like?
        
        ```
        tests:
          - type: http
            url: https://www.google.com
            verification_field: status_code
            success_value:
              - 200
        
          - type: telnet
            host: 127.0.0.1
            port: 22
            sucess_value: connected
        
          - type: command
            command: echo Returned output
            success_value: Returned output
        ```
        
        ### Options: 
        
        This tool curently support three kind of executers. Means you can write these three kind of tests. 
        1. HTTP Executer: Test http requests. 
        2. TELNET Executer: Test telnet. 
        3. COMMAND Executer: Test shell commands on local. 
        
        
        # Contributing
        
        When contributing to this repository, please first discuss the change you wish to make via issue, or any other method with the owners of this repository before making a change.
        
        Please note we have a code of conduct, please follow it in all your interactions with the project.
        
        ## Pull Request Process
        
        1. Ensure any install or build dependencies are removed before the end of the layer when doing a
           build.
        2. Update the README.md with details of changes to the interface, this includes new environment
           variables, exposed ports, useful file locations and container parameters.
        4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
           do not have permission to do that, you may request the second reviewer to merge it for you.
        
        ## Code of Conduct
        
        ### Our Pledge
        
        In the interest of fostering an open and welcoming environment, we as
        contributors and maintainers pledge to making participation in our project and
        our community a harassment-free experience for everyone, regardless of age, body
        size, disability, ethnicity, gender identity and expression, level of experience,
        nationality, personal appearance, race, religion, or sexual identity and
        orientation.
        
        ### Our Standards
        
        Examples of behavior that contributes to creating a positive environment
        include:
        
        * Using welcoming and inclusive language
        * Being respectful of differing viewpoints and experiences
        * Gracefully accepting constructive criticism
        * Focusing on what is best for the community
        * Showing empathy towards other community members
        
        Examples of unacceptable behavior by participants include:
        
        * The use of sexualized language or imagery and unwelcome sexual attention or
        advances
        * Trolling, insulting/derogatory comments, and personal or political attacks
        * Public or private harassment
        * Publishing others' private information, such as a physical or electronic
          address, without explicit permission
        * Other conduct which could reasonably be considered inappropriate in a
          professional setting
        
        ### Our Responsibilities
        
        Project maintainers are responsible for clarifying the standards of acceptable
        behavior and are expected to take appropriate and fair corrective action in
        response to any instances of unacceptable behavior.
        
        Project maintainers have the right and responsibility to remove, edit, or
        reject comments, commits, code, wiki edits, issues, and other contributions
        that are not aligned to this Code of Conduct, or to ban temporarily or
        permanently any contributor for other behaviors that they deem inappropriate,
        threatening, offensive, or harmful.
        
Keywords: python,tests,test_automation
Platform: UNKNOWN
Classifier: Programming Language :: Python
Classifier: Operating System :: OS Independent
Classifier: Intended Audience :: Developers
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Plugins
Classifier: Topic :: Software Development :: Testing
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Natural Language :: English
Description-Content-Type: text/markdown
