Deleting test database in Vapor 3











up vote
3
down vote

favorite












I want to write some integration tests for Vapor 3 server and I need to have clean Postgre database each time I run my tests. How can I achieve this? It seems migrations isn't the right way to go as they've been running once if database doesn't exist yet.










share|improve this question
























  • Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
    – nathan
    Nov 20 at 14:33










  • @nathan and what is the proper place to run this query in vapor3 project?
    – m8labs
    Nov 20 at 16:42






  • 1




    Using XCTestCase ? stackoverflow.com/questions/29822457/…
    – nathan
    Nov 20 at 16:50















up vote
3
down vote

favorite












I want to write some integration tests for Vapor 3 server and I need to have clean Postgre database each time I run my tests. How can I achieve this? It seems migrations isn't the right way to go as they've been running once if database doesn't exist yet.










share|improve this question
























  • Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
    – nathan
    Nov 20 at 14:33










  • @nathan and what is the proper place to run this query in vapor3 project?
    – m8labs
    Nov 20 at 16:42






  • 1




    Using XCTestCase ? stackoverflow.com/questions/29822457/…
    – nathan
    Nov 20 at 16:50













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I want to write some integration tests for Vapor 3 server and I need to have clean Postgre database each time I run my tests. How can I achieve this? It seems migrations isn't the right way to go as they've been running once if database doesn't exist yet.










share|improve this question















I want to write some integration tests for Vapor 3 server and I need to have clean Postgre database each time I run my tests. How can I achieve this? It seems migrations isn't the right way to go as they've been running once if database doesn't exist yet.







swift vapor vapor3






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 at 22:57

























asked Nov 19 at 20:12









m8labs

2,59612126




2,59612126












  • Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
    – nathan
    Nov 20 at 14:33










  • @nathan and what is the proper place to run this query in vapor3 project?
    – m8labs
    Nov 20 at 16:42






  • 1




    Using XCTestCase ? stackoverflow.com/questions/29822457/…
    – nathan
    Nov 20 at 16:50


















  • Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
    – nathan
    Nov 20 at 14:33










  • @nathan and what is the proper place to run this query in vapor3 project?
    – m8labs
    Nov 20 at 16:42






  • 1




    Using XCTestCase ? stackoverflow.com/questions/29822457/…
    – nathan
    Nov 20 at 16:50
















Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
– nathan
Nov 20 at 14:33




Have you tried using raw SQL queries ? Also, drop table is part of the SQL package
– nathan
Nov 20 at 14:33












@nathan and what is the proper place to run this query in vapor3 project?
– m8labs
Nov 20 at 16:42




@nathan and what is the proper place to run this query in vapor3 project?
– m8labs
Nov 20 at 16:42




1




1




Using XCTestCase ? stackoverflow.com/questions/29822457/…
– nathan
Nov 20 at 16:50




Using XCTestCase ? stackoverflow.com/questions/29822457/…
– nathan
Nov 20 at 16:50












1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










Have a look at https://github.com/raywenderlich/vapor-til/tree/master/Tests



This requires a DB to be running before you run the tests, but it reverts all migrations at the start of each test run, which gives you a clean DB each time. (Specifically here)



There's also a docker-compose.yml in the root directory for spinning up a completely isolated test environment on Linux






share|improve this answer





















  • I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
    – m8labs
    Nov 22 at 15:11










  • Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
    – 0xTim
    Nov 23 at 13:01











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381955%2fdeleting-test-database-in-vapor-3%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote



accepted










Have a look at https://github.com/raywenderlich/vapor-til/tree/master/Tests



This requires a DB to be running before you run the tests, but it reverts all migrations at the start of each test run, which gives you a clean DB each time. (Specifically here)



There's also a docker-compose.yml in the root directory for spinning up a completely isolated test environment on Linux






share|improve this answer





















  • I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
    – m8labs
    Nov 22 at 15:11










  • Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
    – 0xTim
    Nov 23 at 13:01















up vote
3
down vote



accepted










Have a look at https://github.com/raywenderlich/vapor-til/tree/master/Tests



This requires a DB to be running before you run the tests, but it reverts all migrations at the start of each test run, which gives you a clean DB each time. (Specifically here)



There's also a docker-compose.yml in the root directory for spinning up a completely isolated test environment on Linux






share|improve this answer





















  • I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
    – m8labs
    Nov 22 at 15:11










  • Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
    – 0xTim
    Nov 23 at 13:01













up vote
3
down vote



accepted







up vote
3
down vote



accepted






Have a look at https://github.com/raywenderlich/vapor-til/tree/master/Tests



This requires a DB to be running before you run the tests, but it reverts all migrations at the start of each test run, which gives you a clean DB each time. (Specifically here)



There's also a docker-compose.yml in the root directory for spinning up a completely isolated test environment on Linux






share|improve this answer












Have a look at https://github.com/raywenderlich/vapor-til/tree/master/Tests



This requires a DB to be running before you run the tests, but it reverts all migrations at the start of each test run, which gives you a clean DB each time. (Specifically here)



There's also a docker-compose.yml in the root directory for spinning up a completely isolated test environment on Linux







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 20 at 20:02









0xTim

806412




806412












  • I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
    – m8labs
    Nov 22 at 15:11










  • Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
    – 0xTim
    Nov 23 at 13:01


















  • I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
    – m8labs
    Nov 22 at 15:11










  • Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
    – 0xTim
    Nov 23 at 13:01
















I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
– m8labs
Nov 22 at 15:11




I've inspected sources and have some concerns - isn't it extremely wasteful to run different instance of the Application (2 times in a row) before each test method? Why don't they use "override class func setUp()" instead?...
– m8labs
Nov 22 at 15:11












Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
– 0xTim
Nov 23 at 13:01




Running the commands (revert and prepare) require an application to boot up. When you provide the application a command it will exit upon completion, so if you do it the way above you don't have much choice for integration tests
– 0xTim
Nov 23 at 13:01


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381955%2fdeleting-test-database-in-vapor-3%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Create new schema in PostgreSQL using DBeaver

Deepest pit of an array with Javascript: test on Codility

Costa Masnaga