Skip to content

Releases: MarketSquare/robotframework-requests

v0.7.2

11 Nov 22:57
02a93c6
Compare
Choose a tag to compare

What's new

v0.7.1

23 Aug 07:17
Compare
Choose a tag to compare

What's new

Fixes

v0.7.0

01 May 18:00
Compare
Choose a tag to compare

What's new

This version includes a new feature for uploading data in streaming mode without loading big files in memory, thanks to @UVV-gh collaboration.
Logging has been refactored and is now ready for further enhancements.

Features

  • More complete logging for requests and responses @lucagiove (#285)
  • Automatically truncate long data in logs except if loglevel is set to debug or trace @lucagiove (#285)
  • Add Get File For Streaming Upload keyword @UVV-gh (#224)

Fixes

Others

Forever Open Source ;)

Thanks to @bulkan (the original author) that moved the repo to @MarketSquare, this allowed me to enhance a lot the Continuous Integration and Community contribution.
Thanks to @UVV-gh that submitted the PR for the new feature and worked with me to make it production ready.
Thanks also to @Hi-Fi that helped me out with GitHub Actions.
Special thanks to @RobotFramework-Italia and Robot Framework Milano meetup for the work done during a meetup sprint.

v0.6.6

06 Apr 09:29
df0f710
Compare
Choose a tag to compare

This is mainly an internal maintenance release, no new features or fixes are visible.
Mainly GitHub workflow changes, code linting and documentation.

Those are the merged pull requests:

#272 Migrated from Travis to GitHub Action, fixed flake8 errors
#269 #268 Improved documentation
#266 Fixed workflow for draft release

v0.6.5

04 Mar 20:29
ad89c73
Compare
Choose a tag to compare

This is mainly an internal maintenance release, no new features or fixes are visible.
Mainly code and tests have been split and moved to different files.

Those are the merged pull requests:

#263 Code cleanup
#262 Pypi publish on new release
#265 Fix deprecation warnings on internal flask server

v0.6.4

14 Feb 09:41
99d1744
Compare
Choose a tag to compare

Fixed #259

New Status Assertion Keywords

21 Jan 22:04
1b37100
Compare
Choose a tag to compare

What's new

Status Should Be

Fails if response status code is different than the expected.
expected_status could be the code number as an integer or as string.
But it could also be a named status code like 'ok', 'created', 'accepted' or 'bad request', 'not found' etc.
The response is the output of other requests keywords like Get Request.
A custom message msg can be added to work like built in keywords.

Request Should Be Successful

Fails if response status code is a client or server error (4xx, 5xx).
The response is the output of other requests keywords like Get Request.
In case of failure an HTTPError will be automatically raised.

Local HTTP Test Server

A local version of flask httpbin server has been integrated in the project for testing purpose.

Removed deprecated and duplicated code, enhanced logs and retry

26 Sep 20:07
c83bbfe
Compare
Choose a tag to compare

What's new

Enhanced log

  • parameters of requests are now dynamically handled
  • headers defined in session are now shown in logs
  • response is logged if standard python/robotframework debug level is enabled (might be verbose)

Retry on specific status codes

  • is now possible to retry the request even for specific response code (eg 502, 503)
  • it is also possible to specify for which method the retry is allowed

This release covered some maintenance on build and tests.

  • deprecated keywords have been removed
  • duplicated code have been managed
  • documentation have been updated a bit