bee-san/pyWhat

Find / add tests for API keys!

Open

#150 opened on Oct 2, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (382 forks)batch import
good first issuehacktoberfest

Repository metrics

Stars
 (6,228 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We have a bunch of regex which do not have tests:

  • Facebook (no idea how to use their API)

  • Twitter (I am bannned from making a bot)

  • GitHub App Token does not exist according to google

  • LinkedIn Client ID - changed to hash

  • LinkedIn Secret Key - changed to hash

  • GitHub Access Token - same as personal access token?

  • Stripe Restricted API Token - cant find

  • Square Access Token - no examples

  • Square OAuth Token - no examples

  • PayPal/Braintree Access Token - no examples

  • MWS Auth Token - no examples

  • Picatic API Key - no examples

  • Google OAuth Access Key - no example

  • Google OAuth ID - no examples

  • StackHawk API Key

  • NuGet API Key

  • SendGrid Token

  • Zoho Webhook Token

  • New Relic Admin API Key

  • New Relic Insights API Key

  • New Relic REST API Key

  • New Relic Synthetics Location Key

  • Microsoft Teams Webhook

  • Google FCM Server Key

  • Discord Webhook

  • Cloudinary Credentials

  • Bitly secret key

  • PyPi Upload Token

  • Shopify Private App Access Token

  • Shopify Custom App Access Token

  • Shopify Access Token

  • Shopify Shared Secret

  • Dynatrace Token

  • Google Cloud Platform API Key

  • Mailchimp API Key

Find some API keys and make some tests! Look here to find our tests, just copy one of them! https://github.com/bee-san/pyWhat/blob/main/tests/test_regex_identifier.py

Contributor guide

Research direction
Examine existing test patterns in test regex identifier.py, find API key samples online or from documentation, and add corresponding test cases.
Tech stack
python
Domain
security
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80