[pytest-dev] py.test implementation on timeline

Ayelet Regev ayelet at fabrixsystems.com
Mon Sep 8 16:29:07 CEST 2014


Hi,

We are developing tests timeline based on py.test.
In our setup:
each test can run multiple times with different configured configuration 
parameters.
some tests thats need to be executed in parallel.
we are using xdist and starting the run-call hook each time our 
pre-required milestones are met.

our configured timeline data:

[
     {
         "test_func_name": "test_cm_delete",
         "timeline_name": "test_cm_delete_working20",
         "cfg": [
             {
                 "comment": "ChannelMapname",
                 "type": "string",
                 "name": "channel_name",
                 "value": "working_20"
             }
         ],
         "dependency": [
             {
                 "id": null,
                 "start_after": null,
                 "sync_type": "event",
                 "sync_interval": 30,
                 "sync_interval_scale": "Sec"
             }
         ]
     },
     {
         "test_func_name": "test_cm_delete",
         "timeline_name": "test_cm_delete_working21",
         "cfg": [
             {
                 "comment": "ChannelMapname",
                 "type": "string",
                 "name": "channel_name",
                 "value": "working_21"
             }
         ],
         "dependency": [
             {
                 "id": "test_cm_delete_working20",
                 "start_after": null,
                 "sync_type": "event",
                 "sync_interval": 30,
                 "sync_interval_scale": "Sec"
             }
         ]
     }
]


*our problems are:*
1) all nodes are started at once.
for each node we need to send some other "cfg" data params to execute 
the test.
we would be happy to use request object as parameter for the tests, but 
we cannot find any relation between the request and the executed test.

2) The other problems we are having related to the fact that each xdist 
slave run in diffrent memory address so we cannot change config object 
on one place to be read by all slaves during execution.
Any suggestions are welcome.




Can you assist us?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20140908/45b92423/attachment.html>


More information about the Pytest-dev mailing list