20203f217e
chore: cede default type ownership and mark deprecated
...
For https://github.com/microsoft/vscode-js-debug/issues/1065
2021-08-03 13:09:27 -07:00
dfd3275e4c
useV3 by default on insiders
2020-05-20 09:34:47 -07:00
9c57d7ce82
Adding support for launching with port = 0
2019-08-19 15:23:53 -07:00
718a640020
feedback
2019-07-08 15:51:29 -07:00
fb067ad1e3
Fixing tests to work in V1
2019-07-08 15:00:46 -07:00
ae0e8df977
Raw merge from v2
2019-07-08 12:11:56 -07:00
1a071b41bf
Fix tests
2019-06-14 15:33:53 -07:00
f97f1c317a
Added new tests to verify webRoot works with any case
2019-05-22 13:39:00 -07:00
533ecc5c08
Stack trace formatting integration tests
2019-04-24 14:13:21 -07:00
a6fddc3763
Applied some new feedback
2019-04-17 10:22:55 -07:00
22d6c8a5bd
Merge pull request #811 from digeff/v1_utility_code
...
Added hit count breakpoints tests and breakpoints utility
2019-04-16 18:00:14 +00:00
7390889540
Added hit count breakpoints tests and breakpoints utility
2019-04-15 23:22:47 -07:00
e0b541ea9e
Files needed from v2 for the hit count breakpoints tests and breakpoints utility
2019-04-15 23:14:58 -07:00
4b4febeffa
Fix race condition in test launch
...
Based on timing, a test could fail because the initialized event fired before the listener was hooked up.
2019-04-15 14:52:10 -05:00
af5ecde83f
Add workaround for race condition
...
We discovered a race condition that doesn't happen often when testing locally, but seems to happen quite often on the CI machines. The issue occurs if a breakpoint set request comes in after the first scriptParsed event, but before the target script is parsed, the adapter tries to use breakOnLoad with an instrumentation breakpoint, but because scripts are already running on the browser, that instrumentation breakpoint will never be hit, and thus the pending breakpoints will never be resolved.
Note that this commit is only a workaround for the tests, and does not fix the underlying issue, which is that breakpoints set during a specific window of time will never actually be set in Chrome.
2019-04-10 16:01:18 -05:00
258cc137fd
update package-lock.json after rebase
2019-04-03 16:03:47 -05:00
11fe2875cd
adding step-in test
2019-04-03 15:55:11 -05:00
3c039cc6b3
Adding step in/out tests
2019-04-03 15:54:04 -05:00
6041707568
Fix a bug with labels and global regex
2019-04-03 15:54:03 -05:00
f07df8967a
Add ability to use block comments for breakpoint labels
2019-04-03 15:54:03 -05:00
70363dc173
Added ability to set breakpoints by label in tests
...
Also updated react test project to use labels.
2019-04-03 15:53:18 -05:00
7ebb82cbd7
Add a "get page by url" function
...
This should be more ideal than "get page 0", though we do have to poll the browser because
we start off every session at "about:blank"
2019-04-03 15:46:50 -05:00
60aba9fa0b
Cherry pick 4b63f95e - Fixing issues with cascading test failures.
...
Some tests were leaving resources open, or not awaiting the teardown.
2019-04-01 16:20:23 -05:00
06df8d2baa
Setting up multi-reporter and increasing the debugClient timeout
2019-03-26 10:32:48 -05:00
4365b97b34
Make sure we await the continue request.
...
Not awaiting the final continue request in the puppeteer tests (or not including it at
all), can cause the test to fail because
the chrome instance will be closed
before the click promise resolves.
2019-03-25 16:44:11 -05:00
d6cc823948
Use local puppeteer chromium version in integration tests
2019-03-20 12:56:02 -05:00
874e0b8d99
Applying PR feedback
2019-03-18 18:00:46 -05:00
109d97ca39
Adding clarifying comment
2019-03-18 15:14:08 -05:00
016fd34c2e
Removing timer function.
...
This function isn't used, and there's a similar function 'promiseTimeout' in core anyway.
2019-03-18 15:07:38 -05:00
21366a3f8c
Adding full react project to source
2019-03-15 18:40:47 -05:00
9efd155096
Adding initial framework integration tests
...
Adds a handful of integration tests for React, and
some tooling to easily use puppeteer in integration
tests in preparation for v2.
2019-03-15 14:46:57 -05:00
f3acc91a56
updating unit test mock, returning promises in integration test teardowns, not waiting to asynchronously kill chrome on windows
2019-01-23 16:46:40 -08:00
6703f2b7d4
updating comment to permalink
2019-01-22 10:04:16 -08:00
13a5474e67
fixing integration tests
2019-01-18 02:12:00 -08:00
142fa8d6c8
Bump -core, update test for -core, 4.10.2 changelog
2018-09-27 11:38:23 -07:00
4c59042cf1
Use nullable `targetTypes` property for advanced debugging configurations.
2018-09-10 13:55:44 -07:00
436ea3eff0
Bump -core and other deps
2018-09-06 11:46:27 -07:00
4f2af39fb0
Fix tests
2018-09-03 21:07:09 -07:00
c54e7fa58b
Fix test linting
2018-06-07 16:29:01 -07:00
ec0a3371d8
Add the supportsLaunchUnelevatedProcessRequest flag to the telemetry.
...
So we know that VS declared capabilty of launching Chrome unelevated.
Also added a unit test.
2018-06-07 14:57:25 -07:00
ecbd0637eb
Switch to devtools-protocol with -core
2018-05-02 10:40:29 -07:00
0aa3b1504b
Upgrade TypeMoq
2018-05-01 16:40:34 -07:00
dd0c948093
Add semicolon tslint rule
2018-03-26 15:20:04 -07:00
09b21a37c2
FIx silent test failure
2018-03-23 18:39:06 -07:00
736af28f46
Use the telemetry collector to append an additional telemetry property for launch request.
2018-03-23 15:11:35 -07:00
ba070649b4
Update tslint
2018-03-22 15:27:57 -07:00
ebcd0b8452
Fix test failing from missing Browser.getVersion mock
2018-03-20 11:55:32 -07:00
6bd498134d
Fix unit test
2018-03-12 12:28:22 -07:00
843b5a1cf9
Fix unit test loc warnings
2018-03-12 09:59:40 -07:00
ad3f4700d2
Use landing page even if breakonload is disabled
2018-03-09 14:15:14 -08:00
Connor Peet
Eric Cornelson
Rob Lourens
Diego Geffner
Michael Crane
Shennie Yao
Shennie Yao
Sasha Joseph
Chance An
Raghav Katyal