pytest-dev / pytest-dev/pytest-xdist

[FR] Pytest-xdist should have its own remote agent

Open
#134 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
287
Avg merge
9h 30m
Merged PRs (30d)
2

Description

[Moved from pytest issue tracker, #2326 (https://github.com/pytest-dev/pytest/issues/2326)]

Hi There,

I started to used pytest not too far ago. And I found the xdist plugin. I would like to run test on a remote windows macine.

I saw in the documentation
(https://pypi.python.org/pypi/pytest-xdist/1.15.0)
the reference for socketserver.py

I checked the source, and found that it is mainly for unix/linux systems.
I tried it on windows 7, python 3.5. I sent only a print command to the remote, and it was printed successfully, but after that it wrote some errors. ...

Then I read the docs further and found that it says that init.py files should put next to my tests as the remoting handles them this way.

So I bet I would be able to rewrite the socketserver.py, but I think it would be better to create an authentic agent.

And of course I would install pytest on the remote as well (to have all the capabilities on the remote too)
As Python is installed on remote, I think there is no reason not install pytest as well.
(instead of socketserver.py third party stuff)

With this the xdist would be more complete.

Kind regards,
George

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names socketserver.py and the pytest-xdist documentation; start by reading the referenced remote-execution path and reproducing the reported Windows 7/Python 3.5 behavior. Clarify the agent protocol and platform requirements before changing code. Done means remote Windows execution works with pytest capabilities without the post-command errors described.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.