@bahmutov/cy-grep 1.4.1 → 1.4.3

package/README.md

@@ -1,4 +1,4 @@
-# @bahmutov/cy-grep ![cypress version](https://img.shields.io/badge/cypress-12.4.1-brightgreen)
+# @bahmutov/cy-grep ![cypress version](https://img.shields.io/badge/cypress-12.5.0-brightgreen)
 
 > Filter tests using substring or tag
 
@@ -19,13 +19,25 @@ All other tests will be marked pending, see why in the [Cypress test statuses](h
 
 If you have multiple spec files, all specs will be loaded, and every test will be filtered the same way, since the grep is run-time operation and cannot eliminate the spec files without loading them. If you want to run only specific tests, use the built-in [--spec](https://on.cypress.io/command-line#cypress-run-spec-lt-spec-gt) CLI argument.
 
-Watch the video [intro to cypress-grep plugin](https://www.youtube.com/watch?v=HS-Px-Sghd8) and study my 🎓 Cypress course [Cypress Plugins](https://cypress.tips/courses/cypress-plugins).
+## Training
 
-Table of Contents
+Watch the video [intro to cypress-grep plugin](https://www.youtube.com/watch?v=HS-Px-Sghd8) and study my 🎓 Cypress course [Cypress Plugins](https://cypress.tips/courses/cypress-plugins):
+
+- [Lesson k1: Set up the test grep plugin](https://cypress.tips/courses/cypress-plugins/lessons/k1)
+- [Lesson k2: Filter the tests using test and suite tags](https://cypress.tips/courses/cypress-plugins/lessons/k2)
+- [Lesson k3: Filter the specs without the tag we want to run](https://cypress.tips/courses/cypress-plugins/lessons/k3)
+- [Lesson k4: Filter the tests to run using several tags](https://cypress.tips/courses/cypress-plugins/lessons/k4)
+- [Lesson k5: Filter the tests to run using OR of several tags](https://cypress.tips/courses/cypress-plugins/lessons/k5)
+- [Lesson k6: Repeat selected tests N times](https://cypress.tips/courses/cypress-plugins/lessons/k6)
+- [Lesson k7: Pick the tests to run in the interactive mode](https://cypress.tips/courses/cypress-plugins/lessons/k7)
+
+## Table of Contents
 
 <!-- MarkdownTOC autolink="true" -->
 
 - [@bahmutov/cy-grep ](#bahmutovcy-grep-)
+  - [Training](#training)
+  - [Table of Contents](#table-of-contents)
   - [Install](#install)
     - [Support file](#support-file)
     - [Config file](#config-file)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bahmutov/cy-grep",
-  "version": "1.4.1",
+  "version": "1.4.3",
   "description": "Filter Cypress tests using title or tags",
   "main": "src/support.js",
   "scripts": {
@@ -12,15 +12,15 @@
   "dependencies": {
     "cypress-plugin-config": "^1.2.0",
     "debug": "^4.3.2",
-    "find-test-names": "1.25.1",
+    "find-test-names": "1.28.1",
     "globby": "^11.0.4"
   },
   "devDependencies": {
-    "cypress": "12.4.1",
+    "cypress": "12.7.0",
     "cypress-each": "^1.11.0",
     "cypress-expect": "^3.1.0",
     "prettier": "^2.8.1",
-    "semantic-release": "^20.1.0",
+    "semantic-release": "^20.1.1",
     "typescript": "^4.7.4"
   },
   "peerDependencies": {

package/src/support.js

@@ -110,7 +110,7 @@ function registerCyGrep() {
       .flatMap((item) => item.requiredTags)
       .concat(configRequiredTags)
       .filter(Boolean)
-    // console.log({ nameToGrep, effectiveTestTags, requiredTestTags })
+    debug({ nameToGrep, effectiveTestTags, requiredTestTags })
 
     const shouldRun = shouldTestRun(
       parsedGrep,
@@ -128,7 +128,7 @@ function registerCyGrep() {
         shouldRun,
       )
     } else {
-      debug('should test "%s" run? %s', nameToGrep, shouldRun)
+      debug('should test without tags "%s" run? %s', nameToGrep, shouldRun)
     }
 
     if (shouldRun) {
@@ -183,20 +183,29 @@ function registerCyGrep() {
     if (typeof configTags === 'string') {
       configTags = [configTags]
     }
+    let requiredTags = options && options.requiredTags
+    if (typeof requiredTags === 'string') {
+      requiredTags = [requiredTags]
+    }
 
     if (!configTags || !configTags.length) {
-      // if the describe suite does not have explicit tags
-      // move on, since the tests inside can have their own tags
-      _describe(name, options, callback)
-      suiteStack.pop()
+      if (!requiredTags || !requiredTags.length) {
+        // if the describe suite does not have explicit tags
+        // move on, since the tests inside can have their own tags
+        _describe(name, options, callback)
+        suiteStack.pop()
 
-      return
+        return
+      }
     }
 
     // when looking at the suite of the tests, I found
     // that using the name is quickly becoming very confusing
     // and thus we need to use the explicit tags
     stackItem.tags = configTags
+    stackItem.requiredTags = requiredTags
+    debug('stack item', stackItem)
+
     _describe(name, options, callback)
     suiteStack.pop()