Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Botsing plugin for Eclipse
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Complementing wizard form validation (#35), verify that the selected execution frame level is compatible with the stack trace in the selected execution log. That is, 0<selected execution frame <max depth in stack trace.
Additionally, we can create a control that allows users to select the concrete frame within the stack trace, for instance using a single-selection combobox populated with the frames in order. User selects the frame and the wizard set its frame position.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component: Botsing Wizard
• Execution Environment: Windows 10, Eclipse Photon
• Reporter: Lars Thomas Boye

Description

I select a folder for the "Class Path" field, but the field remains empty in the wizard. Pressing Finish, nothing happens (no console output, no errors).

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Botsing latest version, Eclipse Photon
• Execution Environment: All platforms (Windows, Linux, MacOS)
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Create an Eclipse plugin for Botsing tool, formely known as Evocrash. This plugin should provide a wizard to configure Botsing and run it over a selected crash log and software libraries. Features:

• Wizard launching should be available on the top STAMP menu, and on the contextual menu (for whatever selection)

• The wizard contains one page that configures Botsing:
  -- classpath of the project under test and all its dependencies. In the first implementation, the wizard permit the multiple selection of a folders and/or jars that constitute the classpath. A second implementation obtain this classpath from the inspection of selected Java project (consulting its classpath). Type: java classpath
  -- Level of the target frame. Type: integer
  -- Directory of the given stack trace. Type: string. The wizard permit to browse the filesystem to locate this folder.

• Upon configuration, the Wizard invokes Botsing. See an example of Java invocation of Botsing.

• Botsing logs are displayed in main Eclipse console

• The wizard enables to store Botsing configurations for future launching, or to reuse existing launching configurations. Create a Botsing launching configuration category.

• Amplified tests are placed in a default location. Wizard should report to users that location.

Steps to reproduce

N/A

Other files and URLs

Relationships

See #19

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Descartes plugin for Eclipse, Botsing plugin for Eclipse
• Execution Environment: Linux, Windows
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Same feature as #17 applied to Descartes and Botsing execution.
1- Capture internal plugin exceptions or the Descartes/Botsing termination code
2- In case of plugin exception or tool execution exception, report to user in dialog.
As in #17, request users to report in STAMP ide tracker or tool tracker depending on the origin of exception.
For Descartes, as users to report in tracker
For Botsing, ask users to report in tracker
For plugin issues, ask users to report in tracker

If possible, visualize these URL as links in the dialog

Steps to reproduce

Other files and URLs

Relationships

#17

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: blocker
• Tool/Service/Component: Stamp IDE 1.0
• Execution Environment: any
• Reporter: Alexander Fedorov [email protected]

Description

The EPL 1.0 is deprecating, consider switching to EPL 2.0

Steps to reproduce

Look through the source base:

• a lot of sources and manifests are missing license info
• there are binary jars without clear origin
• the about.html is not included to the distribution
  and a lot of other EPL violations

Other files and URLs

https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: DSpot Wizard
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogoitia [email protected]

Description

In DSpot Wizard, second page, Amplifiers combo box (multiple selecction), not all DSpot amplifiers are included. Please add all DSpot supported amplifiers:

• StringLiteralAmplifier
• NumberLiteralAmplifier
• CharLiteralAmplifier
• BooleanLiteralAmplifier
• AllLiteralAmplifiers
• MethodAdd
• MethodRemove
• TestDataMutator (deprecated)
• MethodGeneratorAmplifier
• ReturnValueAmplifier
• NullifierAmplifier
• None (default: None)

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component: Descartes Eclipse plugin 1.0.0.201809201413
• Execution Environment: Eclipse Photon, windows 10
• Reporter: Lars Thomas

Description

I have tried to use the Descartes Eclipse plugin. I made a configuration and enabled all mutators. Running, it is unable to compile. Complete console output below. I am able to run Descartes through Maven as per the Descartes instructions.

[INFO] Scanning for projects...
[INFO]
[INFO] -----------------------< no.tellu.lib:tellulib >------------------------
[INFO] Building Tellu Utilities Library 3.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ tellulib ---
[INFO] Deleting E:\Dev\tellu-github\tellulib\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ tellulib ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory E:\Dev\tellu-github\tellulib\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ tellulib ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 69 source files to E:\Dev\tellu-github\tellulib\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.554 s
[INFO] Finished at: 2018-09-20T14:58:40+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project tellulib: Compilation failure
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: Eclipse plugin for Descartes
• Execution Environment: All
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Current Eclipse plugin for Descartes let users to specify that output formats will be generated but it only visualize in the Descartes view the ISSUES report. The PIT code coverage report, despite is generated, is not visualize.
Implement support to visualize:

• Descartes issues (is selected) in the Descartes view (actually implemented, but missing in code to check that that report has generated/requested)
• PIT code coverage report in the PIT view
  Current code just display the content of the index.hmtl found in the target/pit-reports// folder.
  Notice that two reports could be generated:
• Descartes: in folder target/pit-reports//issues/ -> file: index.html
• PIT: in folder target/pit-reports// -> file: index.html

See attached view for an example

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: DSpot
• Execution Environment: Windows/Linux
• Reporter: Jesús Gorronogoitia [email protected]

Description

Check DSpot return code after DSpot execution to check whether an error occur (exit code <> 0).
If so, or whatever a exception is produced after DSpot execution in DSpot plugin (for instance when processing report files), do the following:
1- open a modal error dialog informing the user that an error occurred in DSpot execution. Keep console view with DSpot logs opened:
1a- if error is caused by DSpot execution (exit code <> 0), request user to check DSpot logs and port them in this link: https://github.com/STAMP-project/dspot/issues
1b- if error is caused by DSpot plugin, request user to check Error Log view and report in this link:
https://github.com/STAMP-project/stamp-ide/issues
2- do not process DSpot report files
3- do not render/visualize DSpot view

Steps to reproduce

N/A

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: minor
• Tool/Service/Component: DSpot Plugin for Eclipse, version 21/05/18
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen.3a Release (4.7.3a)
• Reporter: Jesús Gorroñogoitia [email protected]

Description

After executing a DSpot configuration, using the DSpot Wizard, DSpot completes successfully, as observed in the Console logs. Next, the DSpot View should be opened with the visualization of the produced json files, howewer, this view is not visualized. Instead, error logs show the following exception:

java.io.FileNotFoundException: /home/yosu/Projects/STAMP/Git/dhell/dspot-out/hello_app.json (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at java.io.FileInputStream.(FileInputStream.java:93)
at java.io.FileReader.(FileReader.java:58)
at eu.stamp.wp4.dspot.view.DSpotView.parseJSON(DSpotView.java:74)
at eu.stamp.wp4.dspot.execution.launch.DSpotEclipseLaunchConfigurationDelegate$1.run(DSpotEclipseLaunchConfigurationDelegate.java:175)
at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)

Steps to reproduce

Run DSpot Wizard with some configuration, selecting individual tests in Elipse Oxygen in Linux.
See below screenshot, showing the json files produced by DSpot in dspot-out folder

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: major
• Tool/Service/Component: Botsing plugin for Eclipse (last version from sources)
• Execution Environment: Linux
• Reporter: Jesús Gorroñogoitia <jesus.gorroñ[email protected]>

Description

Botsing has been tested on HelloExample project, with this Botsing configuration:

• Test directory: /home/yosu/Projects/STAMP/workspaces/stamp-wp4/HelloException/out
• Execution log file: /home/yosu/Projects/STAMP/workspaces/stamp-wp4/HelloException/logs/HelloException.log
• Exception frame level: 1
• Execution classpath: /home/yosu/Projects/STAMP/workspaces/stamp-wp4/HelloException/dep
• Botsing log output folder: /home/yosu/Projects/STAMP/workspaces/stamp-wp4/HelloException
  However, the followings issues are observed:
• No tests are generated in out folder
• only in logs folder the following files are created:

1. logs/src/main/java/eu/stamp/botsing/config.properties, with no content
2. logs/true/hello/exception/HelloException_ESTest.java with this content:

/*
 * This file was automatically generated by EvoSuite
 * Wed Apr 03 09:55:37 CEST 2019
 */

package hello.exception;

import org.junit.Test;
import static org.junit.Assert.*;

public class HelloException_ESTest {
  @Test
  public void notGeneratedAnyTest() {
    // EvoSuite did not generate any tests
  }
}

Verify that the plugin interfaces the Botsing core correctly and these issues are not caused by a wrong usage of Botsing interfaces. Check to run Botsing in CLI using above configuration to see the results.

Steps to reproduce

Run Botsing on HelloException project using Botsing plugin for Eclipse wizard with about configuration. After execution, refresh HelloException and check the results.

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: botsing alpha-1
• Execution Environment:
• Reporter: Xavier Devroey [email protected]

Description

Hi @jesus-gorronogoitia !

The very first alpha version of the new crash reproduction tool, called botsing (since we reimplemented everything, we changed the name), is available https://github.com/STAMP-project/botsing/. The main to call botsing is available here and the command line parameters are listed here. So very few parameters to provide in the end! :-)

Steps to reproduce

NA

Other files and URLs

See STAMP-project/botsing#4

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: Eclipse plugin for Botsing
• Execution Environment: All
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Implement run configuration editor for Botsing configurations, so that they can be modified and executed from the Eclipse run configurations.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: major
• Tool/Service/Component: STAMP Eclipse plugin for DSpot 1.0.0.201809201413
• Execution Environment: Windows 10
• Reporter: Lars Thomas Boye

Description

First attempt at running DSpot through Eclipse. Default config in the wizard dialog. Console output below. Note that DSpot is currently not working for me from the command line either: STAMP-project/dspot#557

[WARN] 2018-09-26 09:24:37 AutomaticBuilderFactory - No automatic builder specified in configuration, going to default.
[INFO] 2018-09-26 09:24:37 AutomaticBuilderFactory - Default: provided Maven automatic builder.
[INFO] 2018-09-26 09:24:37 MavenAutomaticBuilder - run maven dependency:build-classpath -Dmdep.outputFile=target/dspot/classpath
[WARN] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
[INFO] 2018-09-26 09:24:40 AutomaticBuilderFactory - Selected Maven automatic builder.
[INFO] 2018-09-26 09:24:40 MavenAutomaticBuilder - run maven clean test -DskipTests dependency:build-classpath -Dmdep.outputFile=target/dspot/classpath
[WARN] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
Exception in thread "main" java.lang.RuntimeException: java.io.FileNotFoundException: E:\Dev\tellu-github\tellulib\target\dspot\classpath (Systemet finner ikke angitt bane)
at eu.stamp_project.automaticbuilder.MavenAutomaticBuilder.compile(MavenAutomaticBuilder.java:77)
at eu.stamp_project.utils.Initializer.initialize(Initializer.java:20)
at eu.stamp_project.dspot.DSpot.(DSpot.java:88)
at eu.stamp_project.Main.run(Main.java:57)
at eu.stamp_project.Main.run(Main.java:91)
at eu.stamp_project.Main.main(Main.java:42)
Caused by: java.io.FileNotFoundException: E:\Dev\tellu-github\tellulib\target\dspot\classpath (Systemet finner ikke angitt bane)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(Unknown Source)
at java.io.FileInputStream.(Unknown Source)
at java.io.FileReader.(Unknown Source)
at eu.stamp_project.automaticbuilder.MavenAutomaticBuilder.compile(MavenAutomaticBuilder.java:74)
... 5 more

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component: STAMP Eclipse plugin for Botsing 1.0.0.201810091121
• Execution Environment: Eclipse Photon on Windows 10
• Reporter: Lars Thomas Boye

Description

I have installed the new Botsing plugin, but it doesn't show up in the STAMP menu (Descartes and DSpot are there).

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component: DSPOT
• Execution Environment: Ubuntu 16.04
• Reporter: Assad Montasser, [email protected]

Description

I did a first execution of the tool on SAT4j core project, I had a failure in the console (a PitException). I tried to relaunch the tool in order to change parameters and I got this error box. So I did a Maven clean and a Maven build on the project. As you can see in the screen capture, build was successful. But I still have this error box. So I relaunched Eclipse and tried again, but still the same error box.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open

file .github/ISSUE_DOC.md

To increase visibility, I propose to rename this repo to "stamp-eclipse-plugins".

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: DSpot Wizard for Eclipse
• Execution Environment: All OS
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Reorganize DSpot view content, with a new layout described in dspot_view_layout.txt
dspot_view_layout.txt

Steps to reproduce

N/A

Other files and URLs

DSpot files generated for Jacoco selector
dspot-out.zip

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: major
• Tool/Service/Component: STAMP IDE 1.0
• Execution Environment: any
• Reporter: Alexander Fedorov [email protected]

Description

Without unified formatting it will be very hard to manage deltas for sources and get more contributions from the community.

The options may be commited with the .settings/ folder to get Eclipse IDE support

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Descartes plugin for Eclipse
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Add support to manage multiple Descartes configurations in Wizard, similar to the existing support in DSpot Wizard:

• Create/Store new Descartes execution configurations giving a name
• Reuse existing (saved) Descartes execution configurations, browse them in combo box.
• Create Descartes Launch configurations, so they can also be executed from Eclipse Launch (Run/Debug)

Configurations should be stored in dedicated pom files with names: <project_name>_<configuration_name>_pom.xml

Configuration from wizard should be stored in / read from these pom files.

Form in Eclipse Launch configuration for Descartes Launch (already existing) should show the name of pom file. This form already exist, but displayed pom file is null, and launch name is fixed.

Steps to reproduce

N/A

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component: DSpot plugin for Eclipse
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen
• Reporter: Jesús Gorroñogoitia [email protected]

Description

DSpot Wizard does not appear.
Debugging console shows the following exception:

org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
Caused by: java.lang.NullPointerException
at org.eclipse.core.internal.runtime.FindSupport.findInPlugin(FindSupport.java:233)
at org.eclipse.core.internal.runtime.FindSupport.find(FindSupport.java:100)
at org.eclipse.core.internal.runtime.FindSupport.find(FindSupport.java:61)
at org.eclipse.core.runtime.FileLocator.find(FileLocator.java:85)
at eu.stamp.wp4.dspot.wizard.DSpotWizard.getDefaultPageImage(DSpotWizard.java:76)
at org.eclipse.jface.wizard.WizardPage.getImage(WizardPage.java:150)
at org.eclipse.jface.wizard.WizardDialog.updateTitleBar(WizardDialog.java:1420)
at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1273)
at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1228)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:582)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
at org.eclipse.jface.window.Window.open(Window.java:783)
at eu.stamp.wp4.dspot.wizard.utils.DSpotWizardHandler.execute(DSpotWizardHandler.java:41)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
... 37 more

It seems a problem to load the page default icon.

Steps to reproduce

Launch DSpot Wizard

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: block
• Tool/Service/Component:
• Execution Environment:
• Reporter: Lars Thomas Boye

Description

According to the documentation, there should be a Descartes plugin installable from the updatesite included in this repo, but currently there is only a DSpot plugin.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: Eclipse plugin for Botsing
• Execution Environment: All
• Reporter: Luca Andreatta [email protected]

Description

It should be possible to configure Botsing plugin to have the output to be redirected to a file.

Steps to reproduce

Other files and URLs

Relationships

Depends on issues 28

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

The "verbose", "comments" and "nominimize" are advanced config options.

Thus, I propose to put them in the Advanced config screen.

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: DSpot Wizard for Eclipse, latest version
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen 3
• Reporter: Jesús Gorronogoitia[email protected]

Description

After DSpot computation, DSpot properties view is opened, but not visuaiized as front-end view, so the user has to click on it to visualize it.

Steps to reproduce

Run DSpot using DSpot Wizard with any configuration.

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Once Descartes finds a pseudo-tested method, the workflow is to create an issue so that a tester improves the test.

In the Descartes UI, where the report is shown, one could imagine a button that enables to automatically create an issue.

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: STAMP Eclipse IDE
• Execution Environment: All
• Reporter: Jesús Gorronogoitia [email protected]

Description

Rename STAMP entires (for tools) in Eclipse Run Configuration tree:

• "Botsing" entry is fine: ignore
• "Descartes Launch" entry: rename it to "Descartes"
• "DSpot Launch Configuration" entry: rename it to "DSpot"
  See picture below depicting the current state.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: DSpot and Descartes wizards
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Update Title and description in Wizard pages for DSpot and Descartes:
DSpot Wizard:
Page 1:
Title: Project configuration
Description: Information about the project
Page 2:
Title: DSpot execution
Description: Configuration of the DSpot execution
Descartes Wizard:
Title: Descartes configuration
Description: Configuration of Descartes mutators

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: DSpot plugin for Eclipse
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogotia [email protected]

Description

If a user launches DSpot Wizard on a target project after a previous execution of DSpot it is quite likely that the compiled classes are not available and therefore the sources of code base and tests could not be determined. If so, request to user, using a modal dialog, to build the target project. In dialog, use the target project name to add the following message:
"Codebase/Test sources could not be determined. Please, build the project <project_name> and open this dialog again".
When the user accepts the dialog, close it and close the wizard as well.

Steps to reproduce

Execute DSpot Wizard with a configuration in a target project. Then open again DSpot Wizard on the same project.

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: major
• Tool/Service/Component: STAMP IDE 1.0
• Execution Environment: any
• Reporter: Alexander Fedorov [email protected]

Description

There should be an ability to run mvn clean verify from the root folder to produce Eclipse p2 Repository:

• analyze the dependencies and define target platform
• decide on output build aftifacts and complete manifests
• re-layout repository to the normalized form

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: DSpot Wizard
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogotia [email protected]

Description

Refresh the target project in Package/Project explorer or Navigator views, so the generated folder in user-selected <dspot_view> is visible in the project tree

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Botsing plugin for Eclipse
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Add tooltips to labels or form entries in Botsing Wizard form. Manage validation of form entries as done for the other STAMP tool wizards, to ensure mandatory fields are provided with correct content according to the agreed format.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: minor
• Tool/Service/Component: DSpot Wizard
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogotia [email protected]

Description

If DSpot view is kept opened among different executions of DSpot using the Wizard, previous tab showing DSpot execution information are kept, but empty. Only a tab showing the information about DSpot execution for a selected Selector should be kept.

Steps to reproduce

Execute several times DSpot for different selectors without closing the DSpot view.

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: always
• Severity: feature
• Tool/Service/Component: DSpot Wizard
• Execution Environment: Linux/Windows
• Reporter: Jesus Gorroñogotia <jesus.gorroñogoitia>

Description

Rearrange current PIT selector report content in DSpot view. See below the description of the new content layout. In this description, values to extract from keys are represented as <value(key)>

Notice that in the tab label we should put: Selector: projectName, for example: PIT: hellp_app

Steps to reproduce

Other files and URLs

PIT_Selector_View_Layout.txt

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Eclipse version: 4.8.0 (20180619-1200)
Java version: Oracle 1.8.0_181-b13
System: Ubuntu 18.04 64b
DSpot version: git master branch 04da7f9

When I try to start the Wizard (right click on a module -> STAMP -> DSpot) nothing happen visually. Eclipse then report me the following error in the log:

Bundle: org.eclipse.ui 3.109.100.v20180426-0903
Message: Unhandled event loop exception
Exception:
org.eclipse.e4.core.di.InjectionException: java.lang.ArrayIndexOutOfBoundsException: 2
    at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
    at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318)
    at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252)
    at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:161)
    at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
    at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
    at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
    at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:204)
    at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
    at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
    at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
    at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5686)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1370)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4940)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4518)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1170)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1059)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
    at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:667)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1471)

caused by java.lang.ArrayIndexOutOfBoundsException: 2
    at eu.stamp.wp4.dspot.wizard.DSpotWizardPage1.createControl(DSpotWizardPage1.java:235)
    at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176)
    at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:682)
    at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:574)
    at org.eclipse.jface.window.Window.create(Window.java:426)
    at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
    at org.eclipse.jface.window.Window.open(Window.java:783)
    at eu.stamp.wp4.dspot.wizard.utils.DSpotWizardHandler.execute(DSpotWizardHandler.java:43)
    at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
    at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:93)
    at sun.reflect.GeneratedMethodAccessor378.invoke(null:-1)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
    at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318)
    at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252)
    at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:161)
    at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
    at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
    at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
    at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:204)
    at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
    at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
    at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
    at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5686)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1370)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4940)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4518)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1170)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1059)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
    at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:667)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1471)

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: Descartes, Dspot
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Add tooltips to both DSpot and Descartes Wizard page form fields that explains their purpose. Add the tooltips so they are rendered when hovering the mouse pointer over the field label or over the buttons.
Take the tooltip message from a properties files, so the tooltips can be easily updated without requiring to edit code and compile.

Steps to reproduce

N/A

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity:[feature
• Tool/Service/Component: Descartes plugin for Eclipse
• Execution Environment: Windows/Linux/MacOS
• Reporter: Jesús Gorronogoitia [email protected]

Description

Update Descartes plugin for Eclipse to use latest Descartes version: 1.2.4. I assume you only need to update this version number in the generated pom.xml file.

Steps to reproduce

Other files and URLs

Relationships

see #22

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: [always, sometimes, random]
• Severity: feature
• Tool/Service/Component: DSpot plugin for Eclipse
• Execution Environment: All
• Reporter: Jesús Gorroñogoitia[email protected]

Description

Current DSpot plugin for Eclipse invokes DSpot using its CLI. This forces the plugin to embed the DSpot library, and this is incompatible with the DSpot LGPL license.
Therefore, DSpot plugin for Eclipse should invoke DSpot using its Maven interface.
This has two benefits.
1- The plugin does not ship the DSpot library
2- Using the latest version of DSpot only requires to modify its version in the generated pom.xml file.
In order to use DSpot with Maven interface, follows the following documentation:
DSpot documentation

The way DSpot plugin should work now with DSpot is the following:
1- get Wizard configuration and generate a temporary dspot_pom_<configuration_name>.xml
2- run DSpot using Maven and that configuration.
3- Update Dspot configuration using either the generated pom or the wizard configuration

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: DSpot Wizard for Eclipse
• Execution Environment: Linux/Windows
• Reporter: Jesús Gorroñogoitia[email protected]

Description

Implement the following improvements in DSpot Wizard:
1- Opening wizard: as it takes some seconds for complex projects, show an splash DSpot dialog, informing DSpot is loading meantime the wizard is loaded.
1- Page 1: information about the project.
1a- Add support to specify in dspot.properties the list of test classes to be excluded in a comma separated list of test classes (wildcards are supported):
excludedClasses=eu.supersede.integration.api.adaptation.proxies.test.*,eu.supersede.integration.api.analysis.proxies.test.*
To select test classes use the same control than used in second wizard page to select the Test Classes. User can select packages and/or classes. If package is selected is included in the excludedClasses list with the package name + ".", as shown in the above example.
2- Page 2: DSpot execution:
2a- Replace label "Execution classes" by "Test classes"
2b- In control to select test, allow selection of packages and/or classes. If user select a package, it is added to the list as package_name+".", as in above example for excludedClasses.
3- Page 3: advance options:
3a- by default, no one test case should be selected. It seems that once the user opens this dialog for the first time, all cases are selected. They shouldn't. Next time the user open this dialog, only selected cases should be marked. If user reopen a previous DSpot configuration, only selected test cases should be marked.

Steps to reproduce

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: minor
• Tool/Service/Component: Descartes plugin for Eclipse, latest version
• Execution Environment: Linux
• Reporter: Jesús Gorroñogoitia[email protected]

Description

Descartes configuration is added in generated pom.xml on every run of the wizard, causing the ocurrrence of multiple Descartes configurations within the pom file.

Steps to reproduce

Run the wizard several times over the same Descartes configuration. Analyze the generated pom file.

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: feature
• Reproducibility:
• Severity: major
• Tool/Service/Component: Descartes plugin
• Execution Environment:
• Reporter: Lars Thomas Boye

Description

The issue report, listing pseudo-tested and partially-tested methods, is a big reason to use Descartes. It is currently not generated when using the Eclipse plugin. It is generated when ISSUES is included in outputFormats in the configuration.

Characteristics

• Issue Type: feature
• Reproducibility: N/A
• Severity: feature
• Tool/Service/Component: DSpot/Descartes Wizard plugins
• Execution Environment: Windows/Linux
• Reporter: Jesús Gorroñogoitia [email protected]

Description

Implement validation checks in DSpot/Wizards, so that the next button in page is disable if page content is not correct. Similarly in last page, Finish button should be disabled is last page content is not correct.

Correct content:
1- All mandatory fields are filled.
2- Field content is syntactically correct.

Use Eclipse wizard builtin validation to check wizard page content. Spot the fields showing errors, with tooltips providing details.
See Wizard validation tutorial
Download library from here

Steps to reproduce

N/A

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md

Characteristics

• Issue Type: bug
• Reproducibility: always
• Severity: minor
• Tool/Service/Component: DSpot Plugin for Eclipse, Descartes plugin for Eclipse
• Execution Environment: Linux Tumbleweed, Eclipse Oxygen
• Reporter: Jesús Gorroñogoitia [email protected]

Description

When both plugins (DSpot and Descartes) are installed, there are two STAMP top menus, once including a Dspot submenu, another one including a Descartes submenu

Steps to reproduce

Install both plugins using the STAMP update site and observe the Eclipse top menu

I guess this is cause because both plugins declare the same top menu

Other files and URLs

Relationships

Help on issue template

Preview to follow the link or open file .github/ISSUE_DOC.md