Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sam Van Oort
    @svanoort
    ValueError: 'malformed string'
    @marklz Okay, here's one issue: the use of the ast class is wrong here, apparently
    jmespath.search('*', json.loads(body)) # Better way
    Sam Van Oort
    @svanoort
    Yup, that fixes it!
    Mark Z
    @marklz
    woo-hoo
    tired now, will try in the morning - and if it works, I may be all done
    Sam Van Oort
    @svanoort
    @marklz Ay..... yay. Also, gitter notifications: far more finnicky than I was expecting, boo!
    Mark Z
    @marklz
    @svanoort - got everything (example, unit test, functional test) working for certain value of working
    Functional test reports some errors, but all in a code I haven't touched, and errors vary with runs; most of them are lack of response/wrong responses from webserver or misisng URL
    I suggest that you re-run in known good environment....
    so, if you could look at all of my code, and tell me what to do next, since I've done everything I could think of....
    Sam Van Oort
    @svanoort
    @marklz Excellent -- I'll take a look in the next few days. It'll probably require a little adaptation anyway, since I've changed the world under you with Python 3 support & Unicode changes (don't worry about it, I'll sort it out at merge time).
    Mark Z
    @marklz
    Starting 28-Dec I'll be on the move through 06-Jan, so my replies may be delayed. Fell free to change anything you see fit.
    Sam Van Oort
    @svanoort
    @marklz So... I may have gotten slightly eaten by the holidays, but it looks reasonable to me, I need to sort out the merge conflicts and Python 3 compatibility stuff which will take a little time -- opened svanoort/pyresttest#137 for convenience, I might create a merge branch instead depending though.
    Mark Z
    @marklz
    Sure - just keep in mind that I'm an absolute novice in all things github, so if you need me to do something, please, say so.
    Sam Van Oort
    @svanoort
    @marklz Haha! Absolutely -- I'm taking care of the tricky bits for you here since you're new and it's not so tricky for me. Plus you took a chance and invested a bunch of time in this, which is something to encourage for all possible open source contributors at all costs!
    Sam Van Oort
    @svanoort
    @nitrocode / @burritocode - What considerations/features would make the difference for you in using requests/unittest vs. pyresttest? I'm considering some future changes that bring PyRestTest in closer compatibility with python unittest with svanoort/pyresttest#43 and possibly providing a better better support for pure-python testing (long-term roadmap a year or more away).
    @/all ^ anyone with input on requests/unittest combo vs. PyRestTest welcome to give input!
    Joshua C Elliott
    @jcelliott
    @svanoort I'm not sure what you mean. It seems like the point of pyresttest is so you don't have to write requests+unittest type code.
    Or do you just mean in the underlying implementation?
    Sam Van Oort
    @svanoort
    It seems like the point of pyresttest is so you don't have to write requests+unittest type code.
    @jcelliott ^ yes, precisely, but a number of people who would benefit from PyRestTest are opting to do requests/unittest, and I'd like to see why and what can be done longer-term to make it more attractive to better cover their use cases.
    Mark Z
    @marklz
    @svanoort - thanks for all the work with svanroot/pyresttest#78
    Sam Van Oort
    @svanoort
    @marklz Thank you for your contribution and hard work on that! I wish it hadn't taken quite so long to work out the final kinks for Python 3 compatibility in it, but I held up the release until we could get this in, and I think people will appreciate it!
    PS: anybody who thinks dual python 2/3 support is easy, I'd love a hand ;)
    ^ above is invoking someone that probably does not exist.
    Sam Van Oort
    @svanoort
    @/all Heads-up that version 1.7.0 is available for install via PyPi, which includes support for running on Python 3 (alpha-level so far, don't run it in production and please report any issues), greatly improved Unicode handling, the JMESPath extractor (full query on JSON, usable for extraction and validation) - ChangeLog here https://github.com/svanoort/pyresttest/blob/master/CHANGELOG.md
    ^ er, as of March 5, but I'm realizing there's no way to announce releases
    Nick Humrich
    @nhumrich
    Coming in WAY late here, @svanoort still need help with python3 stuff?
    Sam Van Oort
    @svanoort
    @nhumrich Nah, I'm set now - it works on Py3, complete with unit tests and installation tests :) You're welcome to poke at it for flaws though, certainly
    mravitej
    @mravitej
    hello
    Can we get the output in the CSV/HTML format for the respective RESTful API test case
    mravitej
    @mravitej
    My yaml code look like this
    • test: # create an entity by POST
      • name: "Signin Admin User"
      • url: "/api/v1/user/login"
      • method: "POST"
      • body: '{"username": "ravi", "password": "password", "authtype": "plain"}'
      • headers: {Content-Type: application/json}
      • expected_status: [200]
      • group: "login-func"
    i need this output in a CSV/HTML file to track the results.
    Nisarg Mehta
    @nisargatman
    Hello! I want to use pyresttest with a cronjob on a server to run a bunch of tests every hour. If any of the tests fails, i want to send an email notification yo myself, what is the best way to do this? Thanks for any help!
    Johnny Sung
    @j796160836
    @nisargatman I think your answer is using jenkins, which is include reporting system and task executor. You can assign it execute cycling like cronjob.
    Sam Van Oort
    @svanoort
    @nisargatman @j796160836 If you're using it to test code, better yet use a git hook/commit hook to notify from repo -- https://www.cloudbees.com/sites/default/files/2016-jenkins-world-the_need_for_speed-_building_pipelines_to_be_faster.pdf -- but for monitoring it's designed to be pretty easy to integrate with healthchecks, Munin, etc by just running a shell command and looking at return code
    Harshana Nanayakkara
    @harshana5
    hello
    we have few apis to rest and I was thinking about using pyresttest.
    question 1. our development environments but manage to pip install pip install pycurl
    so do i have to do anything else to get this working in windows ?
    Leonardo J. Caballero G.
    @macagua
    Hi @svanoort are you there?
    Jay
    @jaycloudtechie_twitter
    hi! I am evaluating pyresttest for automating our REST API's .. had a basic query .. in my test YAML file, I don't want to harcode/paste the payload in the "body" attribute, but want to externalize my payload to a external JSON file .. is this supported? this is important because we have API's that have huge payloads and it would be very clumsy to hardcode the payload as value for "body" attribute in test YAML file ..
    above is in context of making a POST request with body ..
    @svanoort
    that's a supported feature as far as I remember... it's been a while since I've been using pyresttest though.
    Jay
    @jaycloudtechie_twitter
    awesome!! thanks Benjamin @netjunki for your quick response and providing the link ..
    Jay
    @jaycloudtechie_twitter
    hi, so far I am having a great time with pyresttest .. automating API tests in a jiffy without breaking any sweat, really amazing framework!! as I move forward on to the next steps, wondering if anyone has experience in any test report publishing framework that we can integrate with pyresttest to show test execution reports in some fancy html format ..
    i can write some basic tooling around current output presented by the framework, but wanted to check if anyone already has some insights on this .. no point in re-inventing the wheel :smile: