[PR #1624] [CLOSED] Add Start Testing #1729

New Issue

GiteaMirror · 2025-11-06T15:59:05-06:00

GiteaMirror commented

2025-11-06 15:59:05 -06:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1624
Author: @dialex
Created: 10/3/2019
Status: ❌ Closed

Base: master ← Head: patch-1

📝 Commits (1)

086a6bb Add Start Testing

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/dialex/start-testing#readme

This is an open-source testing course, created collaboratively by the testing community. This is helpful for anyone that wants to start learning about Testing but is overwhelmed by the vast and scattered information available online.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive. ✅
You have to review at least 2 other open pull requests.
- https://github.com/sindresorhus/awesome/pull/1623 ✅
- https://github.com/sindresorhus/awesome/pull/1620 ✅
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. ✅
Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. ✅
Your entry should be added at the bottom of the appropriate category. ✅
The suggested Awesome list complies with the below requirements. ✅

Requirements for your Awesome list

Has been around for at least 30 days.
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. ✅
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. ✅
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it. ✅
Includes a succinct description of the project/theme at the top of the readme. (Example) ✅
It's the result of hard work and the best I could possibly produce. ✅
The repo name of your list should be in lowercase slug format: awesome-name-of-list. ❌
- I would rather not change the slug of my repo, because I've been developing for over a year, and I don't want to break existing backlinks
- Also, this repo already includes several exceptions to this rule, like:
  - https://github.com/karlhorky/learn-to-program#readme
  - https://github.com/hangtwenty/dive-into-machine-learning#readme
  - https://github.com/ujjwalkarn/Machine-Learning-Tutorials#readme
  - and this is only for the Learn topic
The heading title of your list should be in title case format: # Awesome Name of List. ❌
- Same reason as above
Non-generated Markdown file in a GitHub repo. 🤷‍♂️
The repo should have awesome-list & awesome as GitHub topics ✅
Not a duplicate. Please search for existing submissions. ✅
Only has awesome items. Awesome lists are curations of the best, not everything. ✅
Includes a project logo/illustration whenever possible. ⏳
- Not yet, I'm trying to create one
Entries have a description, unless the title is descriptive enough by itself. It rarely is though. 🤷‍♂️
Includes the Awesome badge. ⏳
- It will have once this PR is approved
Has a Table of Contents section. ❌
- Doesn't apply
Has an appropriate license. ✅
Has contribution guidelines. ✅
Has consistent formatting and proper spelling/grammar. ✅
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough. ✅

Go to the top and read it again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/1624 **Author:** [@dialex](https://github.com/dialex) **Created:** 10/3/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`086a6bb`](https://github.com/sindresorhus/awesome/commit/086a6bbc2c6defae8af780e12194736377e548ec) Add Start Testing ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description  https://github.com/dialex/start-testing#readme This is an open-source testing course, created collaboratively by the testing community. This is helpful for anyone that wants to start learning about Testing but is overwhelmed by the vast and scattered information available online. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** ## Requirements for your pull request - **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. ✅ - **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** - https://github.com/sindresorhus/awesome/pull/1623 ✅ - https://github.com/sindresorhus/awesome/pull/1620 ✅ - You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - This pull request has a title in the format `Add Name of List`. ✅ - Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. ✅ - Your entry should be added at the bottom of the appropriate category. ✅ - The suggested Awesome list complies with the below requirements. ✅ ## Requirements for your Awesome list - **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. ✅ - Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. ✅ - Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new). ✅ - **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) ✅ - It's the result of hard work and the best I could possibly produce. ✅ - The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. ❌ - I would rather not change the slug of my repo, because I've been developing for over a year, and I don't want to break existing backlinks - Also, this repo already includes several exceptions to this rule, like: - https://github.com/karlhorky/learn-to-program#readme - https://github.com/hangtwenty/dive-into-machine-learning#readme - https://github.com/ujjwalkarn/Machine-Learning-Tutorials#readme - and this is only for the **Learn** topic - The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. ❌ - Same reason as above - Non-generated Markdown file in a GitHub repo. 🤷‍♂️ - The repo should have `awesome-list` & `awesome` as GitHub topics ✅ - Not a duplicate. Please search for existing submissions. ✅ - Only has awesome items. Awesome lists are curations of the best, not everything. ✅ - Includes a project logo/illustration whenever possible. ⏳ - Not yet, I'm trying to create one - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. 🤷‍♂️ - Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge). ⏳ - It will have once this PR is approved - Has a Table of Contents section. ❌ - Doesn't apply - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). ✅ - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). ✅ - Has consistent formatting and proper spelling/grammar. ✅ - Doesn't include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. ✅ **Go to the top and read it again.** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-06 15:59:05 -06:00

GiteaMirror closed this issue