microsoft
/
accessibility-insights-web
зеркало из https://github.com/microsoft/accessibility-insights-web.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
accessibility-insights-web/.gitignore

29 строки
391 B
Plaintext
Исходник Обычный вид История

chore: manually update license-check-and-add to 3.0.3 (#1301) * fix copyright header automation * updated some settings based on PR feedback * add copyright on some files
2019-09-27 02:04:14 +03:00
# Copyright (c) Microsoft Corporation. All rights reserved.
# Licensed under the MIT License.
Add Visual Studio working files to things to ignore in git (#1355)
2019-10-03 20:11:06 +03:00
# Visual Studio working files
.vs/
*.suo
*.user
Migrate code to GitHub
2019-01-05 00:29:37 +03:00
# Output of build/deploy tasks
/ref/
/extension/
feat(report package) Implemented report npm package (#1741) * Initial version of the Reporter. Not yet functional * Rename in response to PR feedback * Refactored to new calling style * Cleaned up tslint rules * Prettier fixes * Fixed tslint rules * Wired up report generation and created snapshot * Initial cut of building the package * Added TypeScript types to exported package * Stray file got committed. * Fixed copyright headers * Wired up the cards * Unified embedding of styles * Updated tests for both with issues and with no issues * Moved files from reports/library to reports/package * Reset version to 0.0.1 * Added copyright headers to scan files * Made the code prettier * Added package to ignore list * tslint fix * Simplified build steps * renamed build tasks to package-report * Disabled fabric warnings for report package * Moved integration tests into file that identifies them as such * Removed scanResults from generateHtml call * Moved fabric icon call into factory method. * lint: Added a meanless but blocking semicolon * Pruned report dependencies * Added unit test to ensure versions match * Updated snapshots * Excluded integration test from code coverage * Removed script tag from snapshot * Cleaned up duplication in integration test * Updated external interface * One more interface change s/AxeReportRequest/AxeReportParameters/g * Changed axe-core from default import to * import
2019-11-27 03:10:47 +03:00
/package/
test(combined-report-ui): establish monorepo setup with new empty report-e2e-tests package (#3494) #### Description of changes This PR adds a new packages at `/packages/report-e2e-tests`. We'll be using this as part of the combined-report-ui feature to test report generation as it would work in real usage (ie, across package boundaries and with proper style embedding), but this also has the secondary benefit of setting up a lot of the infrastructure we'll be using for migrating the rest of the repo to the lerna/yarn workspaces monorepo format. Specifically, for generalized changes, it: * Adds a new devDependency on lerna * Establishes a `lerna.json` and a root level package.json `workspaces` property to establish the root of the repo as a yarn worktree/lerna monorepo (similar to the setup that service uses) * Updates a variety of ignore/lint tool rules to ignore build output directories in subdirectories, not just the root * Splits out the parts of `tsconfig.json` that will be shared among packages into `tsconfig.base.json` (the same layout that service uses) Specific to the new `report-e2e-tests` package (empty with a placeholder test for now), it also: * Creates the empty package, set up with typescript/jest/etc and a placeholder test * Adds a root-level `yarn test:report:e2e` that runs the tests * Adds a step to run the tests in CI/PR builds Using yarn workspaces means that `yarn install` from the root like usual will cover all the requirements for installing the new package's dependencies. I used `lerna` to implement `yarn test:report:e2e` mostly as a POC (you could technically invoke `jest --projects packages/report-e2e-tests` and it would work equally well) This PR **does not migrate /src to /packages/web/src** - instead, it leaves package.json to act as *both* the worktree root (the aggregator of workspaces) and *also* an individual workspace root representing web/unified/etc. This is supported by yarn, but not what we want to use long-term, since it's a bit confusing; this is an incremental step on the way towards using a layout closer to what service uses. Out of scope for this PR: * Migrating existing web code to `/packages/web` * Migrating existing report package code to `/packages/report` * Migrating the existing report integration tests to `/packages/report-e2e-tests` * Extracting common Jest configuration to a `jest.config.base.js` like service does (this required a lot of changes, so I left it for a separate PR) #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [x] Addresses an existing issue: 1783601 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-21 00:31:59 +03:00
test: convert mock-adb to .NET (#5720) #### Details This PR migrates `mock-adb` from being a Node.js script packaged into an exe using `pkg` to being a .NET 6.0 console application built as a standalone exe. ##### Motivation The main motivation is to improve the reliability of the unified tests by improving mock-adb performance. The .NET version is more than an order of magnitude faster than the Node.js version due to the high startup time involved to initialize the Node.js runtime, before our code starts running, and mock-adb is invoked tens of times per test for all unified tests of scenarios beyond the "device setup" flow. ##### Context For internal folks, see the recording of our 7/7/22 engineering discussion for more context and team discussion. We considered and rejected a few other approaches, including: * Rewrite in Rust/Go instead of .NET * Move to a different repo as part of the rewrite * Instead of rewriting, rearchitect some of the unified tests to avoid having to shell out to a separate `adb.exe` process so much #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn fastpass` - [no] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2022-07-12 23:03:08 +03:00
bin/
chore: move yarn build:package:* output to match future monorepo layout (#3492) #### Description of changes This migrates the webpack/grunt output for the 2 npm packages in the repo from `/package/package-name/*` to `/packages/package-name/*` (package -> packages) to match where the output will start living with the future migration to a monorepo layout. I verified with a directory diff that `/package/report/drop` before this change and `/packages/report/drop` after this change have identical contents after `yarn build:package:report`. #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [n/a] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-20 01:07:15 +03:00
bundle/
test(combined-report-ui): establish monorepo setup with new empty report-e2e-tests package (#3494) #### Description of changes This PR adds a new packages at `/packages/report-e2e-tests`. We'll be using this as part of the combined-report-ui feature to test report generation as it would work in real usage (ie, across package boundaries and with proper style embedding), but this also has the secondary benefit of setting up a lot of the infrastructure we'll be using for migrating the rest of the repo to the lerna/yarn workspaces monorepo format. Specifically, for generalized changes, it: * Adds a new devDependency on lerna * Establishes a `lerna.json` and a root level package.json `workspaces` property to establish the root of the repo as a yarn worktree/lerna monorepo (similar to the setup that service uses) * Updates a variety of ignore/lint tool rules to ignore build output directories in subdirectories, not just the root * Splits out the parts of `tsconfig.json` that will be shared among packages into `tsconfig.base.json` (the same layout that service uses) Specific to the new `report-e2e-tests` package (empty with a placeholder test for now), it also: * Creates the empty package, set up with typescript/jest/etc and a placeholder test * Adds a root-level `yarn test:report:e2e` that runs the tests * Adds a step to run the tests in CI/PR builds Using yarn workspaces means that `yarn install` from the root like usual will cover all the requirements for installing the new package's dependencies. I used `lerna` to implement `yarn test:report:e2e` mostly as a POC (you could technically invoke `jest --projects packages/report-e2e-tests` and it would work equally well) This PR **does not migrate /src to /packages/web/src** - instead, it leaves package.json to act as *both* the worktree root (the aggregator of workspaces) and *also* an individual workspace root representing web/unified/etc. This is supported by yarn, but not what we want to use long-term, since it's a bit confusing; this is an incremental step on the way towards using a layout closer to what service uses. Out of scope for this PR: * Migrating existing web code to `/packages/web` * Migrating existing report package code to `/packages/report` * Migrating the existing report integration tests to `/packages/report-e2e-tests` * Extracting common Jest configuration to a `jest.config.base.js` like service does (this required a lot of changes, so I left it for a separate PR) #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [x] Addresses an existing issue: 1783601 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-21 00:31:59 +03:00
dist/
chore: move yarn build:package:* output to match future monorepo layout (#3492) #### Description of changes This migrates the webpack/grunt output for the 2 npm packages in the repo from `/package/package-name/*` to `/packages/package-name/*` (package -> packages) to match where the output will start living with the future migration to a monorepo layout. I verified with a directory diff that `/package/report/drop` before this change and `/packages/report/drop` after this change have identical contents after `yarn build:package:report`. #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [n/a] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-20 01:07:15 +03:00
drop/
test: convert mock-adb to .NET (#5720) #### Details This PR migrates `mock-adb` from being a Node.js script packaged into an exe using `pkg` to being a .NET 6.0 console application built as a standalone exe. ##### Motivation The main motivation is to improve the reliability of the unified tests by improving mock-adb performance. The .NET version is more than an order of magnitude faster than the Node.js version due to the high startup time involved to initialize the Node.js runtime, before our code starts running, and mock-adb is invoked tens of times per test for all unified tests of scenarios beyond the "device setup" flow. ##### Context For internal folks, see the recording of our 7/7/22 engineering discussion for more context and team discussion. We considered and rejected a few other approaches, including: * Rewrite in Rust/Go instead of .NET * Move to a different repo as part of the rewrite * Instead of rewriting, rearchitect some of the unified tests to avoid having to shell out to a separate `adb.exe` process so much #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn fastpass` - [no] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2022-07-12 23:03:08 +03:00
obj/
test(combined-report-ui): establish monorepo setup with new empty report-e2e-tests package (#3494) #### Description of changes This PR adds a new packages at `/packages/report-e2e-tests`. We'll be using this as part of the combined-report-ui feature to test report generation as it would work in real usage (ie, across package boundaries and with proper style embedding), but this also has the secondary benefit of setting up a lot of the infrastructure we'll be using for migrating the rest of the repo to the lerna/yarn workspaces monorepo format. Specifically, for generalized changes, it: * Adds a new devDependency on lerna * Establishes a `lerna.json` and a root level package.json `workspaces` property to establish the root of the repo as a yarn worktree/lerna monorepo (similar to the setup that service uses) * Updates a variety of ignore/lint tool rules to ignore build output directories in subdirectories, not just the root * Splits out the parts of `tsconfig.json` that will be shared among packages into `tsconfig.base.json` (the same layout that service uses) Specific to the new `report-e2e-tests` package (empty with a placeholder test for now), it also: * Creates the empty package, set up with typescript/jest/etc and a placeholder test * Adds a root-level `yarn test:report:e2e` that runs the tests * Adds a step to run the tests in CI/PR builds Using yarn workspaces means that `yarn install` from the root like usual will cover all the requirements for installing the new package's dependencies. I used `lerna` to implement `yarn test:report:e2e` mostly as a POC (you could technically invoke `jest --projects packages/report-e2e-tests` and it would work equally well) This PR **does not migrate /src to /packages/web/src** - instead, it leaves package.json to act as *both* the worktree root (the aggregator of workspaces) and *also* an individual workspace root representing web/unified/etc. This is supported by yarn, but not what we want to use long-term, since it's a bit confusing; this is an incremental step on the way towards using a layout closer to what service uses. Out of scope for this PR: * Migrating existing web code to `/packages/web` * Migrating existing report package code to `/packages/report` * Migrating the existing report integration tests to `/packages/report-e2e-tests` * Extracting common Jest configuration to a `jest.config.base.js` like service does (this required a lot of changes, so I left it for a separate PR) #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [x] Addresses an existing issue: 1783601 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-21 00:31:59 +03:00
test-results/
feat(android-signing-binskim): Enable BinSkim on Windows pipeline build (#4126)
2021-04-21 23:22:09 +03:00
analysis/
Spike: Using CSS Modules in React (with generated and ignored typings) (#688) * Introducing CSS modules * Example of using/adding CSS module: no-displayable-preview-features-message component * Manually adding copyright to scss.d.ts file * Use typed-scss-modules to generate typings at build time * Added step in build to generate typings + fixed tests + comment for jest config * Added css module for action and cancel buttons component * Produce reproducible in dev vs using hash in prod * Use ID for E2E tests + remove places where scss typings generation is redundant * Fixed unresolved merge conflict * Fix build for electron * Generate scss typings for unit tests
2019-05-25 01:43:55 +03:00
*.scss.d.ts
fix: resolve e2e test flakiness in cross-origin-iframe.test.ts (#5125)
2022-01-29 03:02:03 +03:00
original-manifest-copy.json
feat(mv3-part7): Convert mv3 extension to use build generated JSON validator (#5975) #### Details Fixes mv3 bug with loading assessments. Repro steps: 1. Open mv3 canary/ dev assessment 2. Try to load assessment file 3. See nothing happens in details view, see following errors in console: ``` exception-telemetry-listener.ts:87 Error compiling schema, function code: const schema2 = scope.schema[2];const schema1 = scope.schema[1];return function validate1(data, {instancePath="", parentData, parentDataProperty, rootData=data}={}){let vErrors = null;let errors = 0;const _errs1 = errors;if(!(((typeof data == "number") && (!(data % 1) && !isNaN(data))) && (isFinite(data)))){validate1.errors = [{instancePath,schemaPath:"#/definitions/nonNegativeInteger/type",keyword:"type",params:{type: "integer"},message:"must be integer"}];return false;}if(errors === _errs1){if((typeof data == "number") && (isFinite(data))){if(data < 0 || isNaN(data)){validate1.errors = [{instancePath,schemaPath:"#/definitions/nonNegativeInteger/minimum",keyword:"minimum",params:{comparison: ">=", limit: 0},message:"must be >= 0"}];return false;}}}validate1.errors = vErrors;return errors === 0;} ``` ``` Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'". ``` ##### Motivation Feature work ##### Context The root cause of this bug is that AJV, the library we use to validate the JSON input of assessment files, requires `unsafe-eval` in in the app's content security policy (see their docs: https://ajv.js.org/security.html#content-security-policy). This isn't a problem in mv2, we just add the appropriate line to the manifest: https://github.com/microsoft/accessibility-insights-web/blob/main/Gruntfile.js#L518. But with mv3, chrome no longer allows extensions to include `unsafe-eval` in their manifest CSP, so this is no longer an option. As a solution, this PR migrates us to use AJV's standalone validation code process instead: https://ajv.js.org/standalone.html. A few changes were necessary to convert to the standalone process: 1. Add json generator package. This allows us to build the validator generation code separately from the rest of the codebase. 2. Add extra steps to mv3 build process to (A) build the validator generation code, (B) run the validation generator, and (C) place the generated validator in the expected file such that it can be accessed by the rest of the code. 3. Add extra logic to `load-assessment-data-validator.ts` to determine if the build generated validator is populated or if we should fallback on using the old, dynamically generated validator. We theoretically could convert all products to use the new, build generated validator and remove the old code, but I decided to only convert the mv3 extension to minimize changes to the other products that share this logic. 5. In the case that we use the build generated validator, also check that the assessments data matches the enabled feature flags. With the dynamically generated validator, we are able to check on the fly which feature flags are enabled/ disabled, and as a result, the schema that the validator checks against excludes any assessments that are behind disabled feature flags. We can't check which flags are disabled when we're generating the validator on build, so instead we include all assessments in the build generated validator schema and separately check in `LoadAssessmentDataValidator.uploadedDataIsValid` that none of the assessments in the uploaded data are behind disabled feature flags. #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn null:autoadd` - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2022-09-03 00:53:19 +03:00
validate-assessment-json.js
chore: move yarn build:package:* output to match future monorepo layout (#3492) #### Description of changes This migrates the webpack/grunt output for the 2 npm packages in the repo from `/package/package-name/*` to `/packages/package-name/*` (package -> packages) to match where the output will start living with the future migration to a monorepo layout. I verified with a directory diff that `/package/report/drop` before this change and `/packages/report/drop` after this change have identical contents after `yarn build:package:report`. #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: #0000 - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [n/a] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS
2020-10-20 01:07:15 +03:00
Initial commit
2018-12-07 03:40:02 +03:00
# Dependency directories
add failure screenshots for failed e2e (#66)
2019-01-17 00:48:32 +03:00
node_modules/
test: add end-to-end test to verify tab stops visualization works (#990) - adds a e2e test for validating `tabstops` visualization on the target page when tabstops are started using adhoc tools.
2019-08-07 00:45:58 +03:00
.DS_STORE
yarn-error.log