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 a hook for serializing/unserializing report sections #111

Closed
pytestbot opened this issue Jan 7, 2012 · 8 comments
Closed

add a hook for serializing/unserializing report sections #111

pytestbot opened this issue Jan 7, 2012 · 8 comments
Assignees
Labels
type: feature-branch new feature or API change, should be merged into features branch type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)


that way we can have more easy serialization of things like
tracebacks, detailed log reports and the like


@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):


Not sure i get it - you can already put arbitrary objects on reports which will be serialized/deserialized.

@pytestbot
Copy link
Contributor Author

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):


but that only covers execnet serializable stuff and things with a crude string conversation
anything more complex is left out

@pytestbot pytestbot added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label Jun 15, 2015
@nicoddemus
Copy link
Member

@RonnyPfannschmidt, can you elaborate on this a bit? 😄

@RonnyPfannschmidt
Copy link
Member

currently we have a very crude serialization/deserialization of test report sections, covering only things that execnet can handle

in order to make report serialization/replay more usefull and more approachable we need a hook for dealing with those

@nicoddemus
Copy link
Member

You mean a hook that would receive an object and return a serializable object (for example a dict containing only basic types)?

This idea would allow #133 to be implemented as a plugin, I think.

@RonnyPfannschmidt
Copy link
Member

yes

@The-Compiler
Copy link
Member

This would be a nice feature, but shouldn't block 3.0. Since it's already over 4.5 years old, I'm removing the milestone entirely.

@The-Compiler The-Compiler removed this from the 3.0 milestone Aug 5, 2016
@RonnyPfannschmidt RonnyPfannschmidt added the type: feature-branch new feature or API change, should be merged into features branch label Jun 28, 2018
fkohlgrueber pushed a commit to fkohlgrueber/pytest that referenced this issue Oct 27, 2018
@nicoddemus
Copy link
Member

Fixed in #4965

mgorny pushed a commit to mgorny/pytest that referenced this issue May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature-branch new feature or API change, should be merged into features branch type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Development

No branches or pull requests

4 participants