Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add acceptance tests #2664

Closed
wants to merge 1 commit into from

Conversation

Lothiraldan
Copy link
Contributor

Following of #2207 and #2643, add some "examples" or "acceptance" test files in the acceptance directory.

They are not yet tested automatically.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.824% when pulling cfb369c on Lothiraldan:acceptancetests into 76c55b3 on pytest-dev:master.

@RonnyPfannschmidt
Copy link
Member

@Lothiraldan sorry for taking so long on this one, i am under the impression that it needs a bit of discussion but i'm currently swamped with other things

@Lothiraldan
Copy link
Contributor Author

No problem, I needed them for my own plugin. Could we keep the pull-request open so we don't forget about it and plugins authors might find the pull-request and use them?

@RonnyPfannschmidt
Copy link
Member

i#ll keep it open until i get to it

@RonnyPfannschmidt RonnyPfannschmidt self-assigned this Aug 22, 2017
@nicoddemus
Copy link
Member

@RonnyPfannschmidt anything else needed here?

@RonnyPfannschmidt
Copy link
Member

@nicoddemus this one follows up with an odea of another pr, but i need to detail handling it

@RonnyPfannschmidt
Copy link
Member

#2207 just got merged and i'm thinking about how to combine with this one i will probably need a bit more time to get to it

@RonnyPfannschmidt RonnyPfannschmidt added the type: enhancement new feature or API change, should be merged into features branch label Jun 15, 2018
@nicoddemus
Copy link
Member

#3623 will probably take this one over or supersede this, correct?

@RonnyPfannschmidt
Copy link
Member

@nicoddemus thanks for the note, i will take a look at pulling them over/integrating them after #3623 is merged as it will take a while to sort them from what we have inside our own examples

@nicoddemus
Copy link
Member

#3636 has also been merged.

@RonnyPfannschmidt
Copy link
Member

@nicoddemus i still need to make time to actually do this ^^

@nicoddemus
Copy link
Member

Oh sure, just a gentle ping! 👍

@RonnyPfannschmidt
Copy link
Member

now that we have the example dir and moved many more elaborate tests there, i wonder if the tests that helped to inspired the structural idea actually still make sense to move in

@nicoddemus
Copy link
Member

I feel the same way, I'll leave up to you to decide. I'm OK with closing this now.

@RonnyPfannschmidt
Copy link
Member

@Lothiraldan i want to thank you again from bringing this up and creating it, it had been a valuable source for sorting out the final implementation

however a side-effect of the final implementation was, that it already includes quite a number of elements and thus this initial idea/demo has been superseded by that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants