npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nerdko/web-services-test-challenge

v1.0.0

Published

web services automation challenge

Downloads

3

Readme

web-services-test-challenge

code challenge for test services automation If you downloaded this package and you are not interested in evaluating my automation skills, sorry, this package is just for that.

Running automation: For running the test, please run the next command: npx cypress run

For running automation with browser open, run the next command: npx cypress run --headless:false

Test will run headless as default and report will be saved in: mochawesome-report\challenge-report.html or mochawesome-report\challenge-report.json

For changing browser or disabling headless mode please reffer to Cypress documentation for all flags

Test definition: Test include failing tests due to issues with the API Swagger states to user $int64 but displays java.lang errors related to the size of the number provided This issue causes put request to fail, since the pet is not found I added a ficture with the crude's base json format so I can worry less about hierarchy when testing and providing a better and easier way to update in the future.