initial commit (#1)

.editorconfig

@@ -0,0 +1,13 @@
+root = true
+
+[*]
+charset = utf8
+end_of_line = lf
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_style = tab
+indent_size = 4
+
+[{*.json,*.yml}]
+indent_style = space
+indent_size = 2

.eslintrc.json

@@ -0,0 +1,6 @@
+{
+  "extends": "brightspace/node-config",
+  "parserOptions": {
+    "sourceType": "module"
+  }
+}

.github/CODEOWNERS

@@ -0,0 +1 @@
+*       @BrightspaceUI/gaudi-dev

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/ci.yml

@@ -0,0 +1,17 @@
+name: CI
+on: pull_request
+jobs:
+  test:
+    name: Test
+    timeout-minutes: 5
+    runs-on: ubuntu-latest
+    steps:
+      - uses: Brightspace/third-party-actions@actions/checkout
+      - uses: Brightspace/third-party-actions@actions/setup-node
+        with:
+          node-version-file: .nvmrc
+          cache: 'npm'
+      - name: Install dependencies
+        run: npm ci
+      - name: Lint (JavaScript)
+        run: npm run lint

.github/workflows/release.yml

@@ -0,0 +1,27 @@
+name: Release
+on:
+  push:
+    branches:
+      - main
+      - '[0-9]+.x'
+      - '[0-9]+.[0-9]+.x'
+jobs:
+  release:
+    name: Release
+    timeout-minutes: 5
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: Brightspace/third-party-actions@actions/checkout
+        with:
+          persist-credentials: false
+      - uses: Brightspace/third-party-actions@actions/setup-node
+        with:
+          node-version-file: .nvmrc
+          cache: 'npm'
+      - name: Semantic Release
+        uses: BrightspaceUI/actions/semantic-release@main
+        with:
+          GITHUB_TOKEN: ${{ secrets.D2L_GITHUB_TOKEN }}
+          NPM: true
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.gitignore

@@ -0,0 +1 @@
+node_modules/

.nvmrc

@@ -0,0 +1 @@
+18

LICENSE

@@ -0,0 +1,201 @@
+Apache License
+						Version 2.0, January 2004
+						http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+	"License" shall mean the terms and conditions for use, reproduction,
+	and distribution as defined by Sections 1 through 9 of this document.
+
+	"Licensor" shall mean the copyright owner or entity authorized by
+	the copyright owner that is granting the License.
+
+	"Legal Entity" shall mean the union of the acting entity and all
+	other entities that control, are controlled by, or are under common
+	control with that entity. For the purposes of this definition,
+	"control" means (i) the power, direct or indirect, to cause the
+	direction or management of such entity, whether by contract or
+	otherwise, or (ii) ownership of fifty percent (50%) or more of the
+	outstanding shares, or (iii) beneficial ownership of such entity.
+
+	"You" (or "Your") shall mean an individual or Legal Entity
+	exercising permissions granted by this License.
+
+	"Source" form shall mean the preferred form for making modifications,
+	including but not limited to software source code, documentation
+	source, and configuration files.
+
+	"Object" form shall mean any form resulting from mechanical
+	transformation or translation of a Source form, including but
+	not limited to compiled object code, generated documentation,
+	and conversions to other media types.
+
+	"Work" shall mean the work of authorship, whether in Source or
+	Object form, made available under the License, as indicated by a
+	copyright notice that is included in or attached to the work
+	(an example is provided in the Appendix below).
+
+	"Derivative Works" shall mean any work, whether in Source or Object
+	form, that is based on (or derived from) the Work and for which the
+	editorial revisions, annotations, elaborations, or other modifications
+	represent, as a whole, an original work of authorship. For the purposes
+	of this License, Derivative Works shall not include works that remain
+	separable from, or merely link (or bind by name) to the interfaces of,
+	the Work and Derivative Works thereof.
+
+	"Contribution" shall mean any work of authorship, including
+	the original version of the Work and any modifications or additions
+	to that Work or Derivative Works thereof, that is intentionally
+	submitted to Licensor for inclusion in the Work by the copyright owner
+	or by an individual or Legal Entity authorized to submit on behalf of
+	the copyright owner. For the purposes of this definition, "submitted"
+	means any form of electronic, verbal, or written communication sent
+	to the Licensor or its representatives, including but not limited to
+	communication on electronic mailing lists, source code control systems,
+	and issue tracking systems that are managed by, or on behalf of, the
+	Licensor for the purpose of discussing and improving the Work, but
+	excluding communication that is conspicuously marked or otherwise
+	designated in writing by the copyright owner as "Not a Contribution."
+
+	"Contributor" shall mean Licensor and any individual or Legal Entity
+	on behalf of whom a Contribution has been received by Licensor and
+	subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+	this License, each Contributor hereby grants to You a perpetual,
+	worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+	copyright license to reproduce, prepare Derivative Works of,
+	publicly display, publicly perform, sublicense, and distribute the
+	Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+	this License, each Contributor hereby grants to You a perpetual,
+	worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+	(except as stated in this section) patent license to make, have made,
+	use, offer to sell, sell, import, and otherwise transfer the Work,
+	where such license applies only to those patent claims licensable
+	by such Contributor that are necessarily infringed by their
+	Contribution(s) alone or by combination of their Contribution(s)
+	with the Work to which such Contribution(s) was submitted. If You
+	institute patent litigation against any entity (including a
+	cross-claim or counterclaim in a lawsuit) alleging that the Work
+	or a Contribution incorporated within the Work constitutes direct
+	or contributory patent infringement, then any patent licenses
+	granted to You under this License for that Work shall terminate
+	as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+	Work or Derivative Works thereof in any medium, with or without
+	modifications, and in Source or Object form, provided that You
+	meet the following conditions:
+
+	(a) You must give any other recipients of the Work or
+		Derivative Works a copy of this License; and
+
+	(b) You must cause any modified files to carry prominent notices
+		stating that You changed the files; and
+
+	(c) You must retain, in the Source form of any Derivative Works
+		that You distribute, all copyright, patent, trademark, and
+		attribution notices from the Source form of the Work,
+		excluding those notices that do not pertain to any part of
+		the Derivative Works; and
+
+	(d) If the Work includes a "NOTICE" text file as part of its
+		distribution, then any Derivative Works that You distribute must
+		include a readable copy of the attribution notices contained
+		within such NOTICE file, excluding those notices that do not
+		pertain to any part of the Derivative Works, in at least one
+		of the following places: within a NOTICE text file distributed
+		as part of the Derivative Works; within the Source form or
+		documentation, if provided along with the Derivative Works; or,
+		within a display generated by the Derivative Works, if and
+		wherever such third-party notices normally appear. The contents
+		of the NOTICE file are for informational purposes only and
+		do not modify the License. You may add Your own attribution
+		notices within Derivative Works that You distribute, alongside
+		or as an addendum to the NOTICE text from the Work, provided
+		that such additional attribution notices cannot be construed
+		as modifying the License.
+
+	You may add Your own copyright statement to Your modifications and
+	may provide additional or different license terms and conditions
+	for use, reproduction, or distribution of Your modifications, or
+	for any such Derivative Works as a whole, provided Your use,
+	reproduction, and distribution of the Work otherwise complies with
+	the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+	any Contribution intentionally submitted for inclusion in the Work
+	by You to the Licensor shall be under the terms and conditions of
+	this License, without any additional terms or conditions.
+	Notwithstanding the above, nothing herein shall supersede or modify
+	the terms of any separate license agreement you may have executed
+	with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+	names, trademarks, service marks, or product names of the Licensor,
+	except as required for reasonable and customary use in describing the
+	origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+	agreed to in writing, Licensor provides the Work (and each
+	Contributor provides its Contributions) on an "AS IS" BASIS,
+	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+	implied, including, without limitation, any warranties or conditions
+	of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+	PARTICULAR PURPOSE. You are solely responsible for determining the
+	appropriateness of using or redistributing the Work and assume any
+	risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+	whether in tort (including negligence), contract, or otherwise,
+	unless required by applicable law (such as deliberate and grossly
+	negligent acts) or agreed to in writing, shall any Contributor be
+	liable to You for damages, including any direct, indirect, special,
+	incidental, or consequential damages of any character arising as a
+	result of this License or out of the use or inability to use the
+	Work (including but not limited to damages for loss of goodwill,
+	work stoppage, computer failure or malfunction, or any and all
+	other commercial damages or losses), even if such Contributor
+	has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+	the Work or Derivative Works thereof, You may choose to offer,
+	and charge a fee for, acceptance of support, warranty, indemnity,
+	or other liability obligations and/or rights consistent with this
+	License. However, in accepting such obligations, You may act only
+	on Your own behalf and on Your sole responsibility, not on behalf
+	of any other Contributor, and only if You agree to indemnify,
+	defend, and hold each Contributor harmless for any liability
+	incurred by, or claims asserted against, such Contributor by reason
+	of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+	To apply the Apache License to your work, attach the following
+	boilerplate notice, with the fields enclosed by brackets "{}"
+	replaced with your own identifying information. (Don't include
+	the brackets!)  The text should be enclosed in the appropriate
+	comment syntax for the file format. We also recommend that a
+	file or class name and description of purpose be included on the
+	same "printed page" as the copyright notice for easier
+	identification within third-party archives.
+
+Copyright 2023 D2L Corporation
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+	http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

README.md

@@ -1,2 +1,73 @@
-# testing
-Utilities for testing front-end components and applications
+# @brightspace-ui/testing
+
+[![NPM version](https://img.shields.io/npm/v/@brightspace-ui/testing.svg)](https://www.npmjs.org/package/@brightspace-ui/testing)
+
+Testing utilities that build upon [@web/test-runner](https://modern-web.dev/docs/test-runner/overview/) but are specifically designed and configured to work with Brightspace components and applications.
+
+## Installation
+
+Install from NPM:
+
+```shell
+npm install @brightspace-ui/testing
+```
+
+## Developing, Testing and Contributing
+
+After cloning the repo, run `npm install` to install dependencies.
+
+### Linting
+
+```shell
+# eslint
+npm run lint
+```
+
+### Testing
+
+```shell
+# lint & run headless unit tests
+npm test
+
+# unit tests only
+npm run test:headless
+```
+
+## Versioning & Releasing
+
+> TL;DR: Commits prefixed with `fix:` and `feat:` will trigger patch and minor releases when merged to `main`. Read on for more details...
+
+The [semantic-release GitHub Action](https://github.com/BrightspaceUI/actions/tree/main/semantic-release) is called from the `release.yml` GitHub Action workflow to handle version changes and releasing.
+
+### Version Changes
+
+All version changes should obey [semantic versioning](https://semver.org/) rules:
+1. **MAJOR** version when you make incompatible API changes,
+2. **MINOR** version when you add functionality in a backwards compatible manner, and
+3. **PATCH** version when you make backwards compatible bug fixes.
+
+The next version number will be determined from the commit messages since the previous release. Our semantic-release configuration uses the [Angular convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular) when analyzing commits:
+* Commits which are prefixed with `fix:` or `perf:` will trigger a `patch` release. Example: `fix: validate input before using`
+* Commits which are prefixed with `feat:` will trigger a `minor` release. Example: `feat: add toggle() method`
+* To trigger a MAJOR release, include `BREAKING CHANGE:` with a space or two newlines in the footer of the commit message
+* Other suggested prefixes which will **NOT** trigger a release: `build:`, `ci:`, `docs:`, `style:`, `refactor:` and `test:`. Example: `docs: adding README for new component`
+
+To revert a change, add the `revert:` prefix to the original commit message. This will cause the reverted change to be omitted from the release notes. Example: `revert: fix: validate input before using`.
+
+### Releases
+
+When a release is triggered, it will:
+* Update the version in `package.json`
+* Tag the commit
+* Create a GitHub release (including release notes)
+* Deploy a new package to NPM
+
+### Releasing from Maintenance Branches
+
+Occasionally you'll want to backport a feature or bug fix to an older release. `semantic-release` refers to these as [maintenance branches](https://semantic-release.gitbook.io/semantic-release/usage/workflow-configuration#maintenance-branches).
+
+Maintenance branch names should be of the form: `+([0-9])?(.{+([0-9]),x}).x`.
+
+Regular expressions are complicated, but this essentially means branch names should look like:
+* `1.15.x` for patch releases on top of the `1.15` release (after version `1.16` exists)
+* `2.x` for feature releases on top of the `2` release (after version `3` exists)