Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add `DebugSessionParamsDataKind` which will allow finer granulation of tests.

See original GitHub issue

Debug request has field data which content depends on dataKind. Currently, there is only one possibility to run/debug tests and it is SCALA_TEST_SUITES kind.

However, for this kind, the data field is an array of strings, for example ["a.b.myTestSuite, "a.b.c.AnotherTestSuite"], which is a very coarse granulation. A single test suite could consist of multiple test cases and it is impossible to represent a test run that consists of single or multiple (but not all) test cases from a particular test suite.

That’s why I’d like to propose another DebugSessionParamsDataKind - (it’s just a working name) SCALA_TEST_CASES. data for this kind can look like TestCases[], where TestCases is defined as

interface TestCases {
  suiteName: string,
  tests: string[]

Assuming that ["a.b.myTestSuite, "a.b.c.AnotherTestSuite"] are test classes in project, such data structure will allow to represent:

  • run for single test within single test suite- [{suiteName: a.b.myTestSuite, tests: ["test 1"]}]
  • run for multiple test within single test suite - [{suiteName: a.b.myTestSuite, tests: ["test 1", "test 3"]}] // “test 2” is omitted
  • run for multiple tests within multiple test suites - [{suiteName: a.b.myTestSuite, tests: ["test 1"]}, {suiteName: a.b.c.AnotherTestSuite, tests: ["test 15"]}]

suiteName together with the values of tests can be used to construct test selector which can be further used to filter out unwanted test cases.

This proposition is based on my experience gained in Over the next days/weeks I’ll try to do some more research or maybe even small proof of concept that will confirm if the proposed interface is sufficient, but I think it’s a good time to open the issue and gather others’ feedback about this.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

adpi2commented, Dec 1, 2021

That would be great.

Also if we change the format of the debug test request we should also add the jvm options (and environment variable) , as was suggested here and here.

A possible format would be:

export interface ScalaTestSelection {
  /** The build target that contains the test classes. */
  target: BuildTargetIdentifier;

  /** The jvm options for the application. */
  jvmOptions: String[];

  /** The environment variables for the application. */
  environmentVariables?: String[];

  /** The fully qualified names of the test classes in this target and the tests in this test classes */
  classes: ScalaTestSuiteSelection[];

where ScalaTestSuiteSelection could be:

export interface ScalaTestSuiteSelection {
  /** The test class to run. */
  class: String;

  /** The selected tests to run. */
  tests: String[];

Also I think we should have a convention that tests= [] means all the tests.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Debugging in Visual Studio Code
Set breakpoints, step-in, inspect variables and more. ... Once a debug session starts, the Debug toolbar will appear on the top of the...
Read more >
Customizing Debug Tool Utilities - IBM
Debug Tool User Exit Data Set to create and edit a data set that Language Environment user exits read to obtain the TEST...
Read more >
Mapping data flow Debug Mode - Azure - Microsoft Learn
Start an interactive debug session when building data flows with Azure Data Factory or Synapse Analytics.
Read more >
Running a Debug Session - Informatica Documentation
The Debugger uses default session parameters for all other parameters that you cannot configure with a debug session. The Debugger Wizard displays a...
Read more >
Unità Debug Your Code | Salesforce Trailhead
Replay debug logs in Visual Studio Code to discover the root cause of errors ... Let's set a checkpoint in the code, rerun...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found