I have the different test cases developed in test environment using CAPL.
Now I want to run all the testcases designed in CANoe. It should run using a button from panel in CANoe.
Can anyone give an alternative solution to access the testcases in panel from just only one button?
There are two ways to achieve this.
Easy way: Go to the configuration of the Test Module. Enable the Start condition using a system variable. Now you can attach this system variable to a control in your Panel and you can start the test case from the panel. In this method, you can only Start a Test case. It is not possible to stop a test case using system variable.
Hard way: You can develop a .NET Panel (how-to available under chapter ".NET Panels") and then access the CANoe config via COM. In this method, you can have complete control over your test cases (start, stop, resume, etc.)
Related
Using ProEnv, I have configured my computer to start the standard debugger in case my Progress application shows a message (press the "Help" button and in the callstack, click on "Debug"), this is done using this ProEnv environment variable:
DLC=C:\PROGRE~1\OpenEdge
My application is started, using the -debugalert switch.
However, now I'm starting working with PDSOE (Progress Developer Studio for OpenEdge) and I would like to start up that debugger, in the mentioned case. I don't know how to do this, because PDSOE is based on Java technology (it's an Eclipse environment).
Does anybody know how to do this?
Thanks in advance
The way to launch the PDSOE variant of the debugger is from within PDSOE, using a "Debug Configuration". If you've run the application this way, the PDSOE debugger is used regardless of whether you use breakpoints or the <debug> button.
If you run the application from a "Launch Configuration", then the <debug> button will launch the standalone debugger.
They're basically functionally equivalent but TL;DR you'll need to run the application using PDSOE's "Debug Configuration".
Double click in the left margin of your source to set a break point (a small blue ball):
Then start your run configuration in debug mode:
You will be prompted to switch to debug perspective.
Add DEBUGGER:INITIATE(). DEBUGGER:SET-BREAK(). anywhere in the code and execute the application (provided you've already run prodebugenable -enable-all from the ProEnv in Admin mode).
I'm running unit tests on my GetModelAsync() and CreateModelAsync() methods in VS17. I then run Assert.Equal checks on the model fields to ensure they match the expected values.
I want to be able to see the final state of my models, which will help me determine why a test is failing or allow me to manually check my models. I'm thinking something similar to tracking variables in the debugger would make sense, although I don't want to actually run the debugger.
Is there a way to do this?
You can write to the console in your tests and it will show up in Test Explorer. You may want to serialize complex objects to JSON first before doing this. For example:
Console.WriteLine(JsonConvert.SerializeObject(myObject));
Note, for Visual Studio's built in test runner, you have to go through a few steps to see the console output. In the Test Explorer window, click the name of your test, then in the results panel click the Output link, which will open a separate window to show the console output. It's all very unintuitive.
Im using VS Web Performance Test Tool.
My Application has a login and few functionalities but doesnt have a logout . I one closes the browser and opens , it asks for login .
Now, i have 5 rows in excel , but only the first is run and it stops.
Please let me know if anyone knows how to make all rows run.
Thanks,
SK
By default, running a Web Performance Test (WPT) only does one execution of the test. A WPT can be called from a Visual Studio Load Test to run it many times by many virtual (i.e. simulated) users (VUs).
A data driven WPT can easily be run more than once by either of two methods.
After the test has been run once, click the "Edit run settings" on the Web Test results viewer. The modified run settings only apply to runs started by clicking the "Click here to run again" and are lost when the Web Test results viewer is closed. See here for more details.
The default can be changed in a .testsettings file. If no such file is already in the solution, then use the context (right click) menu of the solution in Solution Explorer and select Add => New item then follow the prompts to add a Test settings file. The Web test section of the file controls how WPTs are executed. See here for more details.
I am a scilab/xcos newbee. I have a model with multiple parameters I would like to change the block parameters in real time (seen on a real time graph). So I would like the functionality of the TK scale block for multiple parameters within a gui format. At the moment I have a gui which can adjust parameters, but changes to the parameters only take affect when I restart the simulation (as they are only updated once the simulation is finished running).
I have tried to use set_param but I am not sure it is the right tool for the job. It doesn't seem to access my xcos parameters.
Is it possible to control the parameters of an xcos model in real time with the slider and radio button functionality of a gui? How do I update my variables while the simulation is still running?
Thanks in advance.
SciLab/ScicosLab is certainly capable of creating interactive/responsive GUIs ( which you are refering to as "real-time"). Take a look at uicontrol module to learn how it should be implemented. To see some demos pleas run demo_gui() in the console and in the opened window go to the GUI section. For example:
A nice example can be found here and more examples here.
There is also the GUI Builder if you prefer a GUI drag and drop development environment
When I want to run 1 test, I always have to right-click the method declaration and click "Run Test". Is there a way to do this without using the mouse?
See if there are any relevant entries from TestDriven.NET in Tools - Options - Keyboard (for instance, ReSharper adds "ReSharper.ReSharper_UnitTest_ContextRun", which allows to run a unit test method editor cursor is currently in) and bind that to some keyboard shortcut.
If you go to Tool=> Options => Keyboard then you can create a new shortcut key to run the unit test for a method or the complete suite. Just pick up the command from the list and assign a key.
A quick google for "TestDriven.NET keyboard shortcuts" gives a few helpful pages.
http://weblogs.asp.net/nunitaddin/archive/2004/08/30/222447.aspx
http://www.lostechies.com/blogs/jimmy_bogard/archive/2008/02/27/testdriven-net-keyboard-shortcut.aspx