This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
Introduction
============

PyLodge is a framework that integrates the automated tests with Test Lodge. It will update the status of the test cases
in Test Lodge based on the execution status of the automation script. In case of Failed test cases, it will create a
defect in the issue tracker if the project in Test Lodge has the issue tracker configured.

Installation
============

To install pillage, type the following command in the command line

.. code-block:: bash

$ pip install pylodge

Quickstart
==========

The user need to pass 4 basic arguments at the time of instantiating the PyLodge class.
They are the Test Lodge API endpoint URL, Test Lodge project, Test Lodge user name and Test Lodge password.
There are various ways that the user can pass these arguments.
The user can store these values in environment variables and then pass the values at the time of instantiating the
PyLodge class. Once the PyLodge class is instantiated, the user can call any of the following pylodge methods .

**1. fetch_and_save_project_id()**

This method returns the id of the specified test lodge project .

Usage example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],
os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

project_id = pylodge_obj.fetch_and_save_project_id()

**2. create_test_run()**

This method will create a test run in Test Lodge including all test suites in it. It will return the run id of the
created test run.

Arguments:
run_name (optional) : The name of the test run that you want to create in test lodge. if this argument is not passed
pylodge will create a test run in Test Lodge by a default name The default test run name is
\Automated_Test_Run_(Current Timestamp)

Usage example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj.create_test_run(‘Sample_Test_Run’)

**3. fetch_test_run_name()**

This method will get the test run name for the provided run id.

Arguments:
run_id : The run id of the Test run that need to be fetched.

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])
run_id = pylodge_obj. fetch_test_run_name(‘12345’)

**4. fetch_test_run_id()**

This method will get the test run id for the provided test run name.

Arguments:
test_run_name: The name of the Test run that need to be fetched.

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj. fetch_test_run_id(‘Sample_Test_Run’)

**5. update_test_run_name()**

This method will update the test run name provided the run id and new the new test run name .

Arguments:
run_id: The id of the test run that need to be updated.
test_run_name: The new name of the Test run .

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. update_test_run_name(‘12345’,‘Updated_Test_Run’)

**6. delete_redundant_test_runs()**

This method will delete any redundant test runs matching the provided test run name except the latest one.

Arguments:
test_run_name: The name of the Test run which has redundant test runs with the same name.

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. delete_redundant_test_runs(‘My_Test_Run’)

**7. fetch_and_save_test_case_id_from_test_name()**

This method will fetch the executed step id of a executed step in a test run if executed step title is provided

Arguments:
test_name: The title of the test case for which the id needs to be fetched


Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj.create_test_run(‘Sample_Test_Run’)

test_case_id = pylodge_obj. fetch_and_save_test_case_id_from_test_name(‘My_Test_Case_Title’)

**8. mark_test_as_passed()**

This method will mark the executed step in a test run as “Passed” in Test Lodge provided the executed step title.

Arguments:
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj.create_test_run(‘Sample_Test_Run’)

pylodge_obj.mark_test_as_passed(‘My_Test_Case_Title’)

**9. mark_test_as_failed()**

This method will mark the executed step in a test run as “Failed” in Test Lodge provided the executed step title.
It will create a issue tracker ticket if the issue tracker is configured for the project.

Arguments:
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj.create_test_run(‘Sample_Test_Run’)

pylodge_obj.mark_test_as_failed(‘My_Test_Case_Title’)

**10. mark_test_as_skipped()**

This method will mark the executed step in a test run as “Skipped” in Test Lodge provided the executed step title.

Arguments:
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

run_id = pylodge_obj.create_test_run(‘Sample_Test_Run’)

pylodge_obj. mark_test_as_skipped(‘My_Test_Case_Title’)

**11. mark_test_as_passed_runid()**

This method will mark the executed step in a test run as “Passed” in Test Lodge provided the test run id and the
executed step title.

Arguments:
run_id: The run id of the test run which contains the executed step
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. mark_test_as_passed_runid(‘12345’,‘My_Test_Case_Title’)

**12. mark_test_as_failed_runid()**

This method will mark the executed step in a test run as “Failed” in Test Lodge provided the test run id and the
executed step title. It will create a issue tracker ticket if the issue tracker is configured for the project.

Arguments:
run_id: The run id of the test run which contains the executed step
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. mark_test_as_failed_runid(‘12345’,‘My_Test_Case_Title’)


**13. mark_test_as_skipped_runid()**

This method will mark the executed step in a test run as “Skipped” in Test Lodge provided the test run id and the
executed step title.

Arguments:
run_id: The run id of the test run which contains the executed step
test_name: The title of the test case for which the status need to be marked in Test Lodge

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. mark_test_as_skipped_runid(‘12345’,‘My_Test_Case_Title’)

**14. mark_test_status()**

This method will mark the executed step in a test run as “Passed” / “Failed” / “Skipped” in Test Lodge provided
test run name and the executed step title.

Arguments:
test_case_name: The title of the test case for which the status need to be marked in Test Lodge.
test_run_name(optional): The run name of the test run which contains the executed step.
if None, pylodge will assume the created test run as the test run that has the executed test.
status(optional): The execution status of the test. “Passed” / “Failed” / “Skipped” . The default is ‘Skipped’.
test_log(optional): It is possible to pass a runtime log in to this method. If this argument is appropriately set,
then pylodge will also insert the runtime log as a comment for the executed step


Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])
pylodge_obj. mark_test_status(test_case_name=‘My_Test_Case_Title’,test_run_name=‘My_Test_Run’,status=‘passed’)

**15. mark_test_status_multiple()**

This method will mark multiple executed steps in a test run as “Passed” / “Failed” / “Skipped” in Test Lodge provided
executed step ids / titles as list . It will expect either executed step ids or executed step titles as argument.
If you provide one, the other will become optional.

Arguments:
test_case_names: The list of titles of the test cases for which the status need to be marked in Test Lodge.
test_case_ids: The list of ids of the test cases for which the status need to be marked in Test Lodge
test_run_name(optional): The run name of the test run which contains the executed step.
if None, pylodge will assume the created test run as the test run that has the executed test.
status(optional): The execution status of the test. “Passed” / “Failed” / “Skipped” . The default is ‘Skipped’.


Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

 os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. mark_test_status_multiple(test_case_ids=[‘1000’,’1001’,’1002’],test_run_name=‘My_Test_Run’,status=‘passed’)

**15. fetch_and_save_not_run_test_case_ids()**

This method will fetch all the executed steps in a given test run that are “Not Run” as a list . it will return all the ids as list

Arguments:
test_run_name: The run name of the test run which contains the not run executed steps. i

Usage Example::

pylodge_obj = pylodge.PyLodge(os.environ['TESTLODGE_USERNAME'], os.environ['TESTLODGE_PASSWORD'],

os.environ['TESTLODGE_PROJECT'], os.environ['TESTLODGE_API_URL'])

pylodge_obj. fetch_and_save_not_run_test_case_ids(test_run_name=‘My_Test_Run’)


Example Implementation with selenium webdriver, pytest, xdist and redis :
=========================================================================

My example assumes the test automation project directory structure as mentioned below and using pytest

myproject/

pages/

page1.py
page2.py

tests/

\__init__.py
conftest.py

module-1-folder/

test_functional_test_group1.py

module-2-folder/

test_functional_test_group2.py

updatetestlodge.py


The actual tests are implemented as methods inside the test_functional_test_group1.py files. So each of those methods
will have a prefix as ‘test_’ as a standard pytest naming convention and then followed by the test lodge prefix .
For example if test_tc01_create_user() is the automated test, ‘create_user’ will be the associated manual test case
in test lodge and tc01 will be the prefix of that test case.

For our tests we used pytest and redis. The conftest_.py file for our implementation can be found here conftest_ .
Download and start the redis server before running the tests.

.. _conftest: https://gist.github.com/akondapalli/60165ad869f88d4f00bd#file-conftest-py

Once the automated scripts are run, the tests along with the execution status and the logs are saved in to redis keys.
You need to write another python script that will extract these reds keys and update the Test Lodge .
Here_ is the code that should be saved in a .py file and executed after all tests are run.


.. _Here: https://gist.github.com/akondapalli/60165ad869f88d4f00bd#file-updatetestlodge-py
Release History

Release History

0.3.2

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.3.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.3.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.9

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.8

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.7

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.5

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.9

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.8

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.7

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.5

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
pylodge-0.3.2.macosx-10.10-x86_64.exe (83.0 kB) Copy SHA256 Checksum SHA256 any Windows Installer Jun 30, 2016
pylodge-0.3.2.macosx-10.10-x86_64.tar.gz (9.6 kB) Copy SHA256 Checksum SHA256 any Dumb Binary Jun 30, 2016
pylodge-0.3.2.macosx-10.10-x86_64.zip (13.5 kB) Copy SHA256 Checksum SHA256 any Dumb Binary Jun 30, 2016
pylodge-0.3.2-py2.7.egg (12.2 kB) Copy SHA256 Checksum SHA256 2.7 Egg Jun 30, 2016
pylodge-0.3.2.tar.gz (8.9 kB) Copy SHA256 Checksum SHA256 Source Jun 28, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting