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/testchallenge

v1.0.0

Published

test challenge for QA automation

Downloads

2

Readme

testChallenge

test challenge for QA 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

Test definition: Test include comments for better options to use in a real scenario, since I don't have access to the swagger, I cannot make faster custom commands for login and clean up before test execution When possible, test wait for server side communication to complete before running assertion on the UI Focus and should methods are used as waits hooks for test reliability Each element with ID is found by that selector, other elements are found using the nearest parent with an ID or class as selector and then filtering with a contains command for selecting the specific element. By using a should after each element selector allows for maintainability in the future, since the report will have exactly which element was not found or which value changed