Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/debugger-libs.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/UnitTests
AgeCommit message (Collapse)Author
2020-04-25Got RawArray unit tests working for SoftDebuggerd16-7Jeffrey Stedfast
2020-04-25Added unit tests for raw array valuesJeffrey Stedfast
2020-04-16[UnitTests] Try targetting AnyCPU instead of x86 for the test appJeffrey Stedfast
2020-04-16[UnitTests] Re-enable SDB testsJeffrey Stedfast
Fixes https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1090747
2020-04-14[UnitTests] Fixed unit tests for .netcoreJeffrey Stedfast
2020-04-14[UnitTests] more fixesJeffrey Stedfast
2020-04-13[UnitTests] Don't have guids on blank lines in the test sourcesJeffrey Stedfast
2020-04-13[UnitTests] Fixed GetChildSync() and GetAllChildrenSync()Jeffrey Stedfast
2020-03-31[Mono.Debugging.Tests] Updated links to new bugVladyslavKostin
2020-03-31[Mono.Debugging.Tests] Disabled Sdb testsVladyslavKostin
2020-02-21Synchronize ExceptionInfo's in the unit testsJeffrey Stedfast
This should fix the intermittent CatchPoint1 failure for DotNetCore
2020-02-19Added some helpful Assert strings in the unit tests for diagnosing test failuresJeffrey Stedfast
2020-02-11[UnitTests] Added helper GetAllLocalsSync() methodJeffrey Stedfast
This change effectively just makes sure that all of the Local Variable objects are fetched synchronously. When a debugger backend's GetAllLocals() implementation returns an EvalutingGroup dummy variable so that the local variables can be fetched asynchronously, the new GetAllLocalsSync() method will evaluate & replace that EvaluatingGroup dummy variable with the real list of local variables that the unit tests expect to find.
2020-01-08Make the unit tests easier to debugJeffrey Stedfast
2019-12-13Mimic the behaviour of the ide where breakpoints are always added whenGreg Munn
the session is created. Fix timing issue of assigning breakpoints.
2019-12-13Use a different lock to manage breakpointStoreGreg Munn
Fixes VSTS 1026591 SigTerm signal in Mono.Debugging.dll!Mono.Debugging.Client.DebuggerSession::get_Breakpoints+9 `slock` is used throughout DebuggerSession, however in this case we only need to guard against multiple threads assigning an instance of BreakpointStore. Also, since BreakpointStore is thread-safe we can remove the additional locks around it where we lock on enumeration of `breakpointStore`. This fixes the case where one thread dispatches an OnExit (for example) which tries communicate with the debuggee and waits on data from the socket and another thread attempts to clean up breakpoints.
2019-11-19Remove last packages.config from unit test projectAlexander Köplinger
This allows debugger-libs to build with MSBuild-integrated restore.
2019-08-30Ignore invocations count test on .NET Core debuggerRodrigo Moya
2019-08-02Bump .NET Core tests to 3.0Rodrigo Moya
2019-07-22Fix testsnosami
2019-07-05More fixes for the VS debugger backend unit testsJeffrey Stedfast
2019-07-03Updated BreakpointsAndSteppingTests for VS debugger backend now that ↵Jeffrey Stedfast
stepping is done correctly
2019-06-19Revert upgrade of test app projects to .NET 4.7.2, keep them at v4.5Jeffrey Stedfast
2019-06-10Move remaining projects to net472.Kirill Osenkov
2019-06-07[UnitTests] Remove tmp files after we're done with them. (#228)Jeffrey Stedfast
2019-06-06[Mono.Debugging] Improved source checksum logic for UNIX and DOS line endingsJeffrey Stedfast
Since it is possible that the assemblies being debugged could have been compiled on a different system (potentially with different line endings), compute hashes for the source code in 3 formats: 1. The source code file with line endings as-is 2. The source code file with DOS line endings 3. The source code file with UNIX line endings Note: sometimes source code may have mixed line endings, so it is important to calculate the source code as-is and not just canonicalized UNIX and DOS line endings. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/642329 Fixes issue #5260
2019-05-30Added unit test for RenameFile and change logic of Rename to Remove+AddDavid Karlaš
2019-05-24[UnitTests] Updated for fixes to VsCode debugger's catchpoint supportJeffrey Stedfast
2019-05-22[UnitTests] Target netcoreapp2.1 instead of 2.2Jeffrey Stedfast
2019-05-22[UnitTests] Remove work-around for VsCode debugger backend that is no longer ↵Jeffrey Stedfast
needed
2019-05-17[UnitTests] disabled and/or modified some tests for NetCoreDebuggerJeffrey Stedfast
2019-05-14Added DotNetCore test projects and did some refactoring for DotNetCore ↵Jeffrey Stedfast
debugger tests
2019-05-08Split the Cor and Sdb unit tests into separate filesJeffrey Stedfast
2018-06-20Fix TestApp packages path when project built standaloneMikayla Hutchinson
The MD test suite builds this csproj directly, without a solution, and as a result $(SolutionDir) has the magic value '*Undefined*'
2018-06-19Fix regression introduced in 70e94647Mikayla Hutchinson
The slash after $(SolutionDir) was redundant. In addition, this broke the MD unit tests as they build the csproj directly without a solution, so the build could not find the packages directory.
2018-06-15Fix warningsMikayla Hutchinson
2018-06-05Fix warnings in test appMikayla Hutchinson
2018-06-05Suppress unusused variable/member warning noise in test appMikayla Hutchinson
There were about 30 of them... and the debuggers tests need them
2018-06-05Fix sln fileMikayla Hutchinson
2018-06-05Fix tests warningsMikayla Hutchinson
2018-05-30Fix locals for local functionsMikayla Hutchinson
The existing fix (#170) only handled the case where a local function captures locals from the parent scope on a ref struct. This fixes the case where the function does not capture and the case where it creates a class closure.
2018-03-20Fix incorrect path in test projectLluis Sanchez
2018-03-20Fix output dir of test projectLluis Sanchez
2018-01-24Resolve implicit type arguments in array parameterHaruka Matsumoto
ex) Method<T>(T[]), System.Array.IndexOf<T>(T[], T)
2018-01-24Fix a bug in evaluation of lambda typesHaruka Matsumoto
which have nested class in their argument types. ex) System.Func<int, Namespace1.ClassA+ClassB+ClassC>
2018-01-24Add a blank line for consistencyHaruka Matsumoto
2018-01-24[Lambda] Add support for array.Where(), by using array ElementTypeDavid Karlaš
2018-01-24Support this/base reference and local variablesHaruka Matsumoto
inside lambda on Immediate Pad. - Enable to use this/base reference and local variables only if its type is public
2018-01-24Support lambda expressions as method parametersHaruka Matsumoto
on Immediate Pad. - Not access to local variables nor methods defined in user code For example, `intlst.Max(a => -a)`, `intlst.Any(x => x < 0)` can be evaluated.
2018-01-24Support lambda expression with castHaruka Matsumoto
in Immediate Pad only if the lambda satisfies following conditions - Lambda must be used with cast - Not access to any variables nor methods defined in user code For example, `(Func<int>)(()=>50)` can be evalueated, but `() => 50` is not supported.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 07:45:19 +0300