Pytest Xdist parallel execution, prevent recreating the database
I'm trying to speed up the Selenium tests in my python Django web application by using parallel execution of 4 threads (-n=4)
Of the first 4 tests, 3 give the following error:
[test setup] [Test Error Output]
Got an error creating the test database: (1007, "Can't create database 'test1database'; database exists")
I get that I have to specify setup to be run once before parallel test execution, to prevent this multiple attempts at creating the database, but how would I enforce this in pytest xdist configuration?
selenium pytest xdist
add a comment |
I'm trying to speed up the Selenium tests in my python Django web application by using parallel execution of 4 threads (-n=4)
Of the first 4 tests, 3 give the following error:
[test setup] [Test Error Output]
Got an error creating the test database: (1007, "Can't create database 'test1database'; database exists")
I get that I have to specify setup to be run once before parallel test execution, to prevent this multiple attempts at creating the database, but how would I enforce this in pytest xdist configuration?
selenium pytest xdist
add a comment |
I'm trying to speed up the Selenium tests in my python Django web application by using parallel execution of 4 threads (-n=4)
Of the first 4 tests, 3 give the following error:
[test setup] [Test Error Output]
Got an error creating the test database: (1007, "Can't create database 'test1database'; database exists")
I get that I have to specify setup to be run once before parallel test execution, to prevent this multiple attempts at creating the database, but how would I enforce this in pytest xdist configuration?
selenium pytest xdist
I'm trying to speed up the Selenium tests in my python Django web application by using parallel execution of 4 threads (-n=4)
Of the first 4 tests, 3 give the following error:
[test setup] [Test Error Output]
Got an error creating the test database: (1007, "Can't create database 'test1database'; database exists")
I get that I have to specify setup to be run once before parallel test execution, to prevent this multiple attempts at creating the database, but how would I enforce this in pytest xdist configuration?
selenium pytest xdist
selenium pytest xdist
asked Nov 22 '18 at 11:50
CloudCloud
169624
169624
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You can probably have a different database for each one of the threads. The worker_id
fixture allows you to do that
https://github.com/pytest-dev/pytest-xdist#identifying-the-worker-process-during-a-test
@pytest.fixture()
def test_database(worker_id):
return CreateDatabase("test{}database".format(worker_id))
Update
This github issue comment shows a solution to the OP's original problem. It also creates N databases, using a shared template. This brings the interesting twist of synchronizing the access to a shared resource in fixture.
add a comment |
You can use this if you won't be stuck in any problem in the rest of your code:
CREATE DATABASE IF NOT EXISTS test1database;
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430405%2fpytest-xdist-parallel-execution-prevent-recreating-the-database%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can probably have a different database for each one of the threads. The worker_id
fixture allows you to do that
https://github.com/pytest-dev/pytest-xdist#identifying-the-worker-process-during-a-test
@pytest.fixture()
def test_database(worker_id):
return CreateDatabase("test{}database".format(worker_id))
Update
This github issue comment shows a solution to the OP's original problem. It also creates N databases, using a shared template. This brings the interesting twist of synchronizing the access to a shared resource in fixture.
add a comment |
You can probably have a different database for each one of the threads. The worker_id
fixture allows you to do that
https://github.com/pytest-dev/pytest-xdist#identifying-the-worker-process-during-a-test
@pytest.fixture()
def test_database(worker_id):
return CreateDatabase("test{}database".format(worker_id))
Update
This github issue comment shows a solution to the OP's original problem. It also creates N databases, using a shared template. This brings the interesting twist of synchronizing the access to a shared resource in fixture.
add a comment |
You can probably have a different database for each one of the threads. The worker_id
fixture allows you to do that
https://github.com/pytest-dev/pytest-xdist#identifying-the-worker-process-during-a-test
@pytest.fixture()
def test_database(worker_id):
return CreateDatabase("test{}database".format(worker_id))
Update
This github issue comment shows a solution to the OP's original problem. It also creates N databases, using a shared template. This brings the interesting twist of synchronizing the access to a shared resource in fixture.
You can probably have a different database for each one of the threads. The worker_id
fixture allows you to do that
https://github.com/pytest-dev/pytest-xdist#identifying-the-worker-process-during-a-test
@pytest.fixture()
def test_database(worker_id):
return CreateDatabase("test{}database".format(worker_id))
Update
This github issue comment shows a solution to the OP's original problem. It also creates N databases, using a shared template. This brings the interesting twist of synchronizing the access to a shared resource in fixture.
edited Nov 25 '18 at 17:38
answered Nov 22 '18 at 13:15
xvergesxverges
3,18713049
3,18713049
add a comment |
add a comment |
You can use this if you won't be stuck in any problem in the rest of your code:
CREATE DATABASE IF NOT EXISTS test1database;
add a comment |
You can use this if you won't be stuck in any problem in the rest of your code:
CREATE DATABASE IF NOT EXISTS test1database;
add a comment |
You can use this if you won't be stuck in any problem in the rest of your code:
CREATE DATABASE IF NOT EXISTS test1database;
You can use this if you won't be stuck in any problem in the rest of your code:
CREATE DATABASE IF NOT EXISTS test1database;
answered Nov 22 '18 at 17:56
SamarthSamarth
337210
337210
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430405%2fpytest-xdist-parallel-execution-prevent-recreating-the-database%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown