Setting priority on Unit Tests - is it possible?

Is it possible to set a priority level (low, medium, high) to the units within a test package. Not on the test cases, but when the test plan is generated the option "with transaction" is selected. And we are testing the unit/transaction can you set a priority at the unit level so it appears in the workbench (STWB_WORK).
Is so where do you do that?
Thank you
Dan

Dear Daniel,
I think you want to change the status values appearing in the status tab of test plan all the individual test cases.
Go To Tcode STWB_SET.
From here select the status definition and place the status values you are interest in........this will do the needful.
Please reward points if it helps.

Similar Messages

Unit Test Module cannot create repository

DBA has created user with listed permissions in the documentation and Unit test repository creation is still stating basic permissions need to be met. In addition, I now need to upgrade my (nonexistant) repository and the basic permissions are still not met. What exactly does the repository admin require in oder to create a repository?
Additional problems:
When the dba types in the correct sys user password for that user to create the correct permissions through SQL developer, it states they are wrong. How does the sys user login as sysdba through that? That is our best guess as to why it won't recognize the password. This is also why I am asking what our DBA needs to simply get the admin user running.
Also, after the repository is created, what permissions can be removed from that user? With our DBAs, less is more :)
I appreciate any help; I realize this is a duplicate, but following other threads has not yielded results either.
10gr2 DB, 3.0 now 3.1 Sql Developer
Edited by: sinistral on Feb 14, 2012 11:15 AM
Edited by: sinistral on Feb 14, 2012 11:15 AM

Hi sinistral -
Instructions for setting up a unit test repository in a (dba friendly ;) ) locked down environment are in {message:id=3985967}
+That link points directly to the message for minimum permissions set up. Alternatively, A few messages back is one with info on how a dba can set up the roles/permissions as SQL Developer would so you don't get asked for sysdba info and can use the shared repository feature. {message:id=3985438}+
Brian Jeffries
SQL Developer Team
Edited by: bjeffrie on Feb 15, 2012 11:58 AM to include reference to 'full permissions' info.
Edited by: bjeffrie on Feb 15, 2012 12:45 PM to fix links

Call to a possibly undefined method displays when using static function in Unit Test

Hello!
This has been driving me nuts. I am setting up unit tests for a static class which manages a collection of songs. This is how my unit test class looks:
//START CODE
package flexUnitTests {
          import com.myapp.managers.MusicManager;
          import flash.utils.Dictionary;
          import flexunit.framework.Assert;
          public class MyAppManagerTest {
                    [Before]
                    public function setUp():void {
                              var songData:Dictionary = new Dictionary();
                              songData["mn0012345"] = new Dictionary();
                              songData["mn0012345"]["title"] = "All the Pretty Little Horses";
                              songData["mn0012345"]["description"] = "by: American Traditional | Voice, Piano | 3 pages";
                              MusicManager.setSongData(songData);
                    [Test]
                    public function test_getAuthorsBySKU():void {
                              var expected:String = "American Traditional";
                              var given:String = MusicManager.getAuthorsBySKU("mn0012345");
                              Assert.assertEquals(expected, given);
//END OF CODE
You will notice two calls in red above. When I leave them in the code I see a variety of errors which look like this:
"Call to a possibly undefined method '' through a reference with a static type com.myapp..."
And
"Access of possible undefined property '' through a reference with static type com.myapp..."
Then, when I comment out the two lines in red above, these errors go away. Flash Builder seems really flakey to me. Often I notice that the error list varies, how can it just no longer be an error? Where did this new access error come from, in a no related part of the code, by adding or removing a function call to a static class which remains in the import statement.
Note that the MusicManager contains no references to any of the UI mxml that is throwing these errors. It just simply loads data into a few globals and allows you to grab info.
How is my usage of this function making foreign objects inaccessible?
Please help!!! I am really hoping there is an answer but I have a bad feeling the answer is just that Flash Builder is flakey.

I did some more work on the issue above. There are functions with in the MusicManager that call the UserManager to get a user's ID. When I comment out these calls then the access errors go away. Well the user manager has some calls back to mxml that tell the class that changes where made. My best guess is this is where it stems into the code that is randomly throwing errors. But, it compiles fine and runs fine on a device. Is there something with test cases which doesn't invoke the UI?

I can't figure out how to set a breakpoint in a SenTestingKit unit test

I'm learning Cocoa after decades of doing other languages. I'm trying to use SenTestingKit for unit tests. One of my unit tests doesn't work, and I want to set a breakpoint to figure out why. So far, I haven't figured out how to do this.
I found Chris Hanson's instructions for how to do this, but he apparently wrote them for an earlier version of Xcode, and I don't know enough to adapt them.
I am writing a tutorial document for writing a simple Cocoa App using Xcode 3.1, git, SenTestingKit, and OCMock. It's at http://xorandor.com/FirstCocoaApp. I've got it up to the point of trying to debug a unit test, and I'm stuck there.
I also couldn't figure out how to have Xcode run the unit tests while building the application. Again, Chris' instructions didn't quite do it, and I don't know enough to figure out the rest.
So, if you know how to do this, please give me some hints. I'll put those into my tutorial, so that the next people who need this can find it.
Thanks,
Pat

I figured out more of my problem, but I haven't solved it yet.
What happens is that, after I create a test case, I try to run it with a breakpoint. After I start the program, Xcode turns the breakpoint from blue (meaning active) to orange (meaning that it can't set the breakpoint).
Several people have said to turn off the Lazy symbol loading preference. I did that, and that didn't fix the problem.
I wrote up a detailed list of steps that I took at http://www.xorandor.com/DebugQuestion.txt
I also put a copy of the project file at http://xorandor.com/MyProject.tar
If anyone has any suggestions on what to try next, please let me know.
Thanks,
Pat

Possible to have multiple cluster members in the same JVM (for unit tests)?

Hi,
I'm wondering if it's possible to simulate multiple cluster members inside of a single JVM. I'm looking to unit test my code and it would be great to write cases for various boundary conditions.
This could certainly be done with multiple JVMs but would be more difficult to run in something like cruise control etc.
TIA,
Danny

Hi Danny,
I do not know how to accomplish what you are asking for and run several Coherence nodes in a single JVM, but I have written a JUnit base class that starts a configurable number of nodes (each in its own JVM) and provides some other useful methods for unit/integration testing with Coherence, such as method to clear all caches or to load test data from the CSV file.
It is still a work in progress and you might need to tweak things a bit to make it work in your environment, but it will at least give you a head start.
Shoot me an email if you are interested and I'll send it to you (you can find my email in my profile).
Regards,
Aleks

[svn:osmf:] 10517: Last set of unit tests for ListenerProxyElement.

Revision: 10517
Author:   [email protected]
Date:     2009-09-22 15:47:18 -0700 (Tue, 22 Sep 2009)
Log Message:
Last set of unit tests for ListenerProxyElement.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/proxies/ListenerProxyElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/proxies/TestListenerProxy ElementAsSubclass.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/utils/DynamicListenerProx yElement.as

Revision: 10517
Author:   [email protected]
Date:     2009-09-22 15:47:18 -0700 (Tue, 22 Sep 2009)
Log Message:
Last set of unit tests for ListenerProxyElement.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/proxies/ListenerProxyElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/proxies/TestListenerProxy ElementAsSubclass.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/utils/DynamicListenerProx yElement.as

Unit Testing

Hi All,
I would like to inform to all, can any one explain to me the concept of Unit testing in FICO and how it should be drawn? If possible send any dcoumentation for this focus to my mail id: [email protected]
Thanks with regards,
Bala

Hi
refer below reward if helps
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
We use different software during testing. Most commonly use are
Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:-
1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the data)
http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
Unit test issues
The unit tools test all SAP development work that handles business object processing for the connector. Also, the unit test tools enable you to test the interaction of your work with the ABAP components of the connector. The test tools allow you to test your development work as an online user (real-time) only.
Note:
It is important to understand the differences between testing the connector as an online user and testing the connector as if operating as a background user.
The differences between testing the connector as an online user or as a background user are described as follows:
Memory--When testing a business object, the connector must log into the SAP application.
      The connector runs as a background user, so it processes in a single memory space that is never implicitly refreshed until the connector is stopped and then restarted (therefore it is critical in business object development to clear memory after processing is complete). Since you are an online user, memory is typically refreshed after each transaction you execute.
      For more information, see Developing business objects for the ABAP Extension Module. Any problems that may occur because of this (for example, return codes never being initialized) are not detected using the test tool; only testing with the connector will reveal these issues.
Screen flow behavior--Screen flow behavior is relevant only when using the Call Transaction API. The precise screen and sequence of screens that a user interacts with is usually determined at runtime by the transaction's code. For example, if a user chooses to extend a material master record to include a sales view by checking the Sales view check box, SAP queries the user for the specific Sales Organization information by presenting an additional input field. In this way, the transaction source code at runtime determines the specific screen and its requirements based on the data input by the user. While the test tool does handle this type of test scenario, there is a related scenario that the test tool cannot handle.
      SAP's transaction code may present different screens to online users versus background users (usually for usability versus performance). The test tool only operates as an online user. The connector only operates as a background user. Despite this difference, unit testing should get through most of the testing situations.

Unit testing and integration testing

hello 2 all,
what is the diff bet unit and integration testing? in sap what is unit teesting consists of and integration testing consists of what?
is this the work of test engineers r whose work is this?
take care
love ur parents

Hi Sameer,
Unit Testing
A unit test is a procedure used to validate that a particular module of source code is working properly from each modification to the next. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is
separate from the others; constructs such as mock objects can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users.
Integration testing
Integration testing can proceed in a number of different ways, which can be broadly characterized as top down or bottom up. In top down integration testing the high level control routines are tested first, possibly with the middle level control structures present only as stubs. Subprogram stubs were presented in Section 2 as incomplete subprograms which are only present to allow the higher level control routines to be tested. Thus a menu driven program may have the major menu options initially only present as stubs, which merely announce that they have been successfully called, in order to allow the high level menu driver to be tested.
Top down testing can proceed in a depth-first or a breadth-first manner. For depth-first integration each module is tested in increasing detail, replacing more and more levels of detail with actual code rather than stubs. Alternatively breadth-first would proceed by refining all the modules at the same level of control
throughout the application. In practice a combination of the two techniques would be used. At the initial stages all the modules might be only partly functional, possibly being implemented only to deal with non-erroneous data. These would be tested in breadth-first manner, but over a period of time each would be
replaced with successive refinements which were closer to the full functionality. This allows depth-first testing of a module to be performed simultaneously with breadth-first testing of all the modules.The other major category of integration testing is bottom up integration testing where an individual module is
tested from a test harness. Once a set of individual modules have been tested they are then combined into a collection of modules, known as builds, which are then tested by a second test harness. This process can continue until the build consists of the entire application.
In practice a combination of top-down and bottom-up testing would be used. In a large software project being developed by a number of sub-teams, or a smaller project where different modules were being built by individuals. The sub-teams or individuals would conduct bottom-up testing of the modules which they were
constructing before releasing them to an integration team which would assemble them together for top-down testing.
I think this will help.
Thanks ,
Saptarshi

Reporting unit test duration over builds

We have a set of unit tests which perform standard operations in our software, spinning up the application, creating data...
What we would like to do is create a line chart to show the running time of individual tests across builds, so we can show how code changes are altering system performance.
Is this possible? This is just a quick question before we spend resources to investigate how to do it.
Thanks in advance

As part of the Test result output we are getting TRX files. TRX files are just XMLs. You can write an XSLT transformation to present the data in the format you need. A nice thing about XSLT is that it has built-in aggregation, grouping, sorting etc capabilities
Few more options in detail given below.
http://richhewlett.com/2012/05/24/exporting-an-html-report-from-your-vstfs-test-results/
http://social.technet.microsoft.com/wiki/contents/articles/2061.how-to-create-reports-for-tfs-2010-test-results.aspx
Cheers, Senthilraj

How to debug in dedicated unit test client

Hello,
We have a setup where we do all development in client 100, but have a separate client for unit tests. Since this is the client holding relevant test data, we would like to debug in this client.
How can I achieve this in Eclipse, do I need to create two projects (one for each client) and open the object twice, or is it possible to setup using debug configurations or something similar?
Regards

Hi Matthias,
in Java you need OS privileges to debug Java code running on any Java application server (and additionally set up the Java VM in debug mode and stuff like that). And once you have OS privileges, you can of course debug all Java VM processes/threads on the machine, regardless which application context they are currently running for.
In ABAP you do NOT need any kind of OS privileges in order to debug. All you need is a user in the system/client with debug privileges, which is big advantage in terms of privilege separation. ABAP debugging on customer systems for example, which is a quite normal thing, would be much harder to realize, if we require any kind of OS privileges.
To cut a long story short:
As a user is required with debugging privileges in any ABAP system/client for ABAP debugging, it is not possible to realize a remote debugging in ABAPinEclipse just by specifying SID/client of the remote ABAP system.
So you need to logon to the ABAP system/client (and set breakpoints there) in order to debug. And as the system/client logon to the ABAP backend in ABAPinEclipse is conceptually linked to a project, you need to have an open project for those ABAP system/clients you want to debug in.
Regards,
Christoph Stoeck, ABAP Language

Using SQLCMD variables in SQL Server Unit Test Project

Is it possible to use SQLCMD variables in my SQL Server Unit Test Project? In my test initialize script I'd like to set a database name variable, something like this:
:SETVAR MyDatabase "mydatabase"
SELECT * FROM [$(MyDatabase)].[mytable]
but I get syntax errors when I run the test. Any suggestions how I can get this to work.
Result Message: Initialization method
myTest.TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException:
Incorrect syntax near ':'..

Hi Kevin,
What is the error?
This should work only thing i could see is no scheme specified.
SQL Server uses dbo as default schema.
In your case:
:SETVAR MyDatabase "mydatabase"
SELECT * FROM [$(MyDatabase)].dbo.[mytable]
Also check your instance collation if its Case sensitive then specify database and table name as exact case.
Example:
:SETVAR MyDatabase "[mydatabase]"
:setvar schemavar "[dbo]"
:setvar tablevar "[mytable]"
SELECT * FROM $(MyDatabase).$(schemavar).$(tablevar)

SQL Developer 3.0 Unit Testing

Hi folks,
Firstly, let me say thanks for all the hard work that has gone into the improvements made in SQL Developer 3.0. I've been trailing EA3 for the past few days, and am so far very impressed.
My development team are particularly interested in the improvements made to the Unit Test module. We have previously created a number of tests/test suites in 2.1, but when we select to connect to the old test case repository schema, 3.0 tells me that it can not find the repository. (Apologises, I do not have my development box in front of me, so I can't quote the exact message).
Is there anything I can do to get it to recognise the old repository? I'd prefer not to have to recreate all of our existing tests...
Thanks in advance,
Nick

Hi Mikka,
Only simple PL/SQL Records are currently supported i.e. those that do not contain repeating or optional components and where all the components are themselves supported. This restriction is in place due to the fact that we use JDBC as the parameter passing mechanism which does not directly support the PL/SQL Record type.
ANYTYPE and ANYDATA are not currently supported as they have a dynamic value type and therefore must be programmatically set. In the future, it may be possible to support these through the dynamic value and and validation features.
This will remain so for the final version.
Regards,
Richard

Best way to Unit test Modules?

I am working on a Project where the main app is a separate Flex project and then there are several Modules each having their own unit tests. What is the best recommended way of setting up something like this in terms of test runners? I would like to have one test runner that loads all others?

I have never unit tested just a controller. I have always done end to end testing with the systems I have worked on, so I am coming from a different viewpoint than yourself. I would tend to think that just running a full unit test all the way to your database would be the best test. You will be more likely to find the issues with your program if you are testing with an environment as similar to production as possible.
After running a test you can either purge the data you entered from your test by having sql scripts run against the db, or if this is difficult just reload the database from its original backup. You would probably be able to purge the data quicker than reloading the database from my experience, but it depends on your complexity of the sql scripts.
best of luck.

Performance test from unit tests

Hi;
I tried to apply the principle TDD at the level of perf test of an J2ee application and this from units tests.
I thus used the tool JUnitPerf but regrettably with this tool I must to modify my unit test for the update of the sequence of a test and it propose nobody management of waiting time between every call of a unit test.
Q : Know a tool more complete, stable and maintained which allows to write of the perf tests from unit test ?
Regards;

Hi John,
The testing will depend on the scenario's configured in SAP, which are to be tested. As scenario vary from customer to customer, it is not possible to send a document with screen shot, as these are confidential documents. However, the write-up below should be able to give some clueon the same.
<b>Different Type of Testing are as under</b>:
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Running unit tests on inline hardware custom device

How to do unit tests for Inline Hardware Custom Devices?
I get this error after creating a unit test.
Possible reason(s):
Cannot connect to the target. Please ensure that the VI Server setting is enabled and deployed to the target. Also, make sure that the port number is correct and that this machine is allowed to connect through VI Server.

wegunterjrASI,
I have a few follow up questions for you to gain a better understanding of your application:
1). What are you using to do the unit test (NI’s unit test framework or VI tester from JKI)?
2). What are you conducting the unit test on (RT Driver or something on the host machine)?
3). Are the unit test VIs under the target in the LabVIEW project?
4). Are you able to run a simple unit test?
Screenshots are always appreciated.
Regards,

Setting priority on Unit Tests - is it possible?

Similar Messages

Maybe you are looking for