Unit & Parallel testing

Hai All,
Can anyone tell me the difference between Unit testing and Parallel testing.
Thanks in advance,
Kiran.

I understand that Unit Testing is the first step in the testing process, and is usually conducted by the programmer to ensure that a program operates as defined by the User. The programmer generally creates their own test cases, inputs the data to the program and verifies the results.
Parallel Testing is managed by the Users and is usually the last test before a system goes live. If the new system is replacing an existing one, both systems are operated side by side for a pre-determined period of time to ensure that the output from both systems is the same, or that any differences are expected.
If the application is a new one, then Parallel Testing is usually combined with a Simulated Work Environment.
Hope it helps.
Br
Fabiano

Similar Messages

How do I establish a telnet session with unit under test?

I am going to the next step as a novice and moving from serial communications to ethernet on my unit under test. I have been all over the help and discussion forums etc and cannot find an answer. I need to open up a telnet session with my unit under test and keep it open to send commands back and forth for control of the unit. Can anyone give me a hint of how I am to establish this communication? I have the IP address and I am using port 23 but I just get the session started and then immediately closed. The sequence of events will be: start the session, the unit will reply with a username and then password, after that I need the session to remain open so I can send commands as if I am sitting at the serial port. When complete the session will then be terminated. Thanks in advance for any help.

If you want to do telnet using plain TCP, you need to do everything yourself, including the telnet options negotiation.
RFC 854 should have most of what you need (look towards the bottom).
Most likely, the server will propose a few options, which you should either accept or reject depending on your needs.
Easiest is probably to use a packet sniffer on a regular telnet session, then dissect the negotiation to see what that particular server wants.
RFC 990 has a list of telnet options, look for the section labeled "ASSIGNED TELNET OPTIONS".
It should be simple to write some code that negotiates with one particular host. It will be more difficult to write a full-blown telnet client that does general negotiations with any type of telnet server.
I have a small program that telnets to a router to do some configuration. The only thing I reply to the proposed options is:
"\FF\FD\03\FF\FE\01\r\n" (In \-codes). Translated: "Don't suppress go ahead, Do echo".
(FF=IAC "Interpret as command", FD=Do, FE=Don't, 01=echo, 03= suppress go ahead.)
LabVIEW Champion . Do more with less code and in less time .

Using Labwindows CVI Version 10.0.1 USB communication with FTDI FT2232D to unit under test.

Communication with unit under test works fine in hypterminal after I downloaded virtual driver from FTDI site.
Never done any USB communication before in LabWindows CVI. What functions can I use in labwindows CVI?

Since the device presents itself as a COM port (pretty standard with the FTDI chips) you should be able to use the RS-232 library in CVI. OpenComConfig() will open a connection to the device, ComWrt() will write data to it, and the various ComRd() functions can be used to read the responses back.

Interface used for payroll parallel testing

Hi,
What is the interface used for payroll parallel testing?
when payroll parallel testing will be done?

Hello,
Parallel testing is running payroll in two systems the older and the new one.
we do this before live of new sap payroll.
client wants the same results as the traditional system gives to parallel run is required and comparision is done
Regards

Parallel testing in payroll

Hi All,
I just started working on SAP project with Parallel testing. Can any body write the process of " Combine SAP,s Wage Type Reporter with Excel " to compare and asses differences between legacy system's payroll results and configure change on SAP
plz consider this as urgent
Regards
Octavious

There should be a selection of ratings next to this answer where you can rate the answer.
The concept for parallel running checking is to run the Legacy Payroll and store the relevant data for every employee. Then run the SAP Payroll (for the same period) store the same data and compare the two. I would recommend that this is done for at least three periods. Once there are no differences then you are OK to go. The minimum number of periods is two and this should never be compromised. (Note that these runs can be compressed. In other words three periods parallel running can actually be run in a few weeks, as long as the legacy data has been stored and retained.) The rationale behind the number of runs is:
Run 1 will highlight loading and initiating problems.
Run 2 should prove that the loading problems have been resolved. This will also display any problems that were masked by load problems. I find that this run also highlights differences in processes and errors in the Legacy system.
Run 3 will be the first real clean run, because the differences between the systems should have been resolved and a good test that the two systems are really in line.
To compare the results from the system I have found spreadsheets acceptable. As noted in other responses the first check should be on Net Pay but you also need to compare the detail of the pay (in case there are compensating errors). To obtain data from SAP we developed summary payslips that produced the required figures in one line. This can easily then be down-loaded to a spreadsheet and (big advantage) can be produced from a simulation run. The most useful figures I have found are (UK-specific):
Net Pay
Gross Pay
Tax Deduction
NI Deduction
Overtime
Pensions
Other Deductions
Then compare the data first check for big differences (i.e. greater than £100 either way) and then all the way down to no differences.
All easily said but a lot of work but vital and should not be skimped it will pay off in the end.
Hope all that helps
Regards
Rob

Question on parallel testing 1000 UUT

I am starting to consider an architecture for a TS system that needs to handle several hundred, and possibly over a thousand UUT's simultaneously in parallel from a single PC w 4GB ram
Anyone have examples of such a high socket count system? Any tips, caveats? I am concerned about a TS system being capable of that.
I expect that I would need a custom Serial Entry dialog (perhaps table based) and that I would NOT display the exectuion/report window for the UUTS although I may include option to display that for a *specfic* UUT selected by the operator
Regards
Vijay

NIExpert,
As Lindsey's link and Jiggawax's tests indicate, there is no hard limit on the number of threads/UUTs you can run at once, but your computer will likely protest well before you hit 1000 UUTs. Even if your machine does not hit an OS-enforced thread limit, memory will become a concern, and the tests will likely take much longer to complete due to your computer's CPU having to split its time between all of these threads.
I agree with Jiggawax that if you want to do this on one machine you would probably be best off doing the tests in waves so that not all 1000 units are being tested at once. It sounds like you'd want the Parallel model so that you can start/stop individual UUTs as needed, and the Parallel model would probably be better suited for this type of approach anyway.
The other option would be to distribute the test to multiple machines. That would allow you to test more devices at once and test them more quickly since the CPUs will not need to switch between as many threads. This approach has a few advantages, for example,you gain hardware redundancy (if a tester goes down, you have other machines that can continue to test). Of course, the trade-off is that there is additional expense in maintaining another tester.
This sounds like an interesting application and I hope you are able to find an approach that best suits your needs. Let us know if you have any more questions about it.
Daniel E.
TestStand Product Support Engineer
National Instruments

What's the best Preferred Execution System setting for parallel testing run from TestStand

I configured what vi's I think need to be reentrant, but I am not sure what choice for "Preferred Execution System" is best for the vi's in my TestStand sequence that's going to run in parallel. Can anyone advise?
Thanks!

Hi mike_22,
This option should not matter unless you have a LabVIEW VI with parallel code blocks. If this is the case, you can set your VI to Other 1 or Other 2. Please take a look at this knowledgebase for further explanation.
Cheers,
Kelly R.
Applications Engineer
National Instruments

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.

Batch Test With Parallel TestSequences

Need a little assistance programming a TestStand batch sequence also containing test sequences which must run in parallel with synchronization.
I have a panel containing multiple UUT. Each UUT consist of 2 parts. The test may be divided into 4 groups:
1: Common start up test and programming
2a: Specific test and calibration on part 1
2b: Specific test and calibration on part 2
3: Common test and calibration of complete UUT
My application runs with the batch model (which I normally use and is familiar with), but must in this case also use parallel testing for each UUT. I need to be able to synchronize the parallel test sequences like they where running in normal batchmodel. I also need at some point to synchronize the to parallel sequences for all UUTs.
I’ve succeeded doing that with the enclosed sequence, but I am not sure it’s the right solution. Would like some comments.
Attachments:
BatchTestSeqWithParallelTestSequences.seq ‏72 KB
BatchTest With ParallelTestSequences.jpg ‏82 KB

A couple things regarding your issue:
You should be fine with just the Parallel or Batch model. Personally, if you don't need to switch out UUTs dynamically then I would go with the Batch model. Why? Because then you can use synchronized sections. Synchronized sections give you the ability to run a particular section of your sequence file (i.e. several or a single step) in Parallel, Sequentially or One Socket Only. With the parallel model you can kind of get there by using Locks and Queues. Look in the TestStand Reference Manual under Appendices A and B for more info on the Batch model and synchronized sections. To access the TestStand Reference Manual go to Start>>All Programs>>National Instruments>><TestStand>>>Documentation>>Manuals.
Regarding your VIs and how they would handle each socket. I don't think it's a good idea to make a different VI for each socket. Just have some sort of case inside the VI that if 3 comes in the set the right wires to populate your switching or COM functions. For instance: Lets say that Socket 1 is executing and comes to the step to call the com_port.vi. One of the parameters for that VI could be the socket number. Inside the VI you set the desired com port to read or write based on that parameter. You can set the parameter in TestStand by using RunState.TestSockets.MyIndex (that will return the socket you are on).
In fact you wouldn't even need the logic in your com_port.vi. I would assume that one of the parameters to that VI would be a VISA session to your COM ports. In TestStand you use the LabVIEWIOControl datatype which has property of DeviceName. If you set that parameter to be '"COM" + Str(RunState.TestSockets.MyIndex)' then you will achieve the same thing as passing COM3 if you were in TestSocket 3.
Anyhow, this is just a few ideas for you. Obviously you have to implement what makes sense.
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

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

The battery of my iPhone 5 easily discharges even if not in use. This started 11 months after purchase. The unit passed the Apple Battery Health Test Protocol but the performance showed otherwise. What is the problem and how do I solve it?

The battery of my iPhone 5 easily discharges even when not in use. The unit was tested by Apple and passed the Battery Health Test although the performance showed otherwise. The battery deterioration started 11 months after purchase and is not covered by Apple warranty. What is the problem of the iPhone5 and would appreciate suggestions on how to address this problem. By the way, I have a 2 year old iphone 4S with a battery performance as good as when it was bought two years ago.

Hi there Dan Laven,
You may find the information in the article below helpful.
iPhone and iPod touch: Charging the battery
http://support.apple.com/kb/ht1476
About battery life and the battery
Battery life and number of charge cycles vary by use and settings. Find more information about batteries for iPhone and iPod.
Find information on how long the battery is expected to last between charges.
Rechargeable batteries have a limited number of charge cycles and may eventually need to be replaced.
-Griff W.

ABAP unit: test classes part of prod. code

Hi all,
I've read <a href="https://weblogs.sdn.sap.com/pub/u/266">Thomas Weiss</a>'s weblog: <a href="/people/thomas.weiss/blog/2004/12/17/a-spotlight-on-abap-unit-part-1 Spotlight on ABAP Unit Part 1</a>.
I posted a question there, but apparently Thomas can't answer at the moment, and since I'm impatient for getting someone's opinion, I reckon we can discuss that topic here :^)
As explained in the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c1be1003-0701-0010-3795-f87160de6483">NetWeaver Developers Guide Using ABAP</a>, the test classes are part of the program under test (PUT):
In ABAP Unit, test classes are part of the production code of the TU. This avoids problems arising from the test code being separate from the production code:
- Programs and tests must be kept synchronized.
- You have to ensure that the test and program code are transported together.
- External test code only enables black box tests with an outside perspective of the tested program.
Since the test code is part of the production code, it is easy to keep the unit tests and the
production code up to date if the latter is changed.
Although the test code and the production code are transported through the system landscape, ABAP unit tests do not increase the load on the production system. By default, the test code is not compiled in the production system. Therefore, the test code can never be executed in the production system.
On the other hand, this idea is quite different from what suggested by other unit testing frameworks.
For instance, the documentation of <a href="http://www.ruby-doc.org/stdlib/libdoc/test/unit/rdoc/classes/Test/Unit.html">Test::Unit - Ruby Unit Testing Framework</a> reads:
Its handy to collect a bunch of related tests, each test represented by a method, into a common test class that knows how to run them.
The tests will be in a separate class from the code theyre testing for a couple of reasons. First of all, it allows your code to stay uncluttered with test code, making it easier to maintain. Second, it allows the tests to be stripped out for deployment, since theyre really there for you, the developer, and your users dont need them. Third, and most importantly, it allows you to set up a common test fixture for your tests to run against.
Regarding the advantages outlined by NetWeaver Developers Guide:
- Programs and tests might be kept synchronized even if they don't belong to the same unit of code.
- Moreover, you could assure that the test and program code are transported together by saving them in the same package.
- And quite frankly, I don't have a thourough understanding of the reason why external tests only allow black box tests with an outside perspective.
What are your opinions on this?
Regards, Davide

Hi,
when I started unit testing with JUnit I was quite surprised that SAP groups the tests with the production code. But now I actually really like it. It has a few advantages:
- Good tests serve as an excellent documentation so why not bundling them together.
- If you want to look at the tests they are easy to find.
- I write all my class tests as local classes. I found out that it really helps me to focus on writing tests only for the class under test. Sometimes it is quite easy to forget the "unit" and write integration tests again.
Regarding your question:
>And quite frankly, I don't have a thourough understanding of the reason why external tests only allow black box tests with an outside perspective.
Usually I would not use the term black box testing in this context. Maybe you mean that it is easy to access private attributes, methods when you group class and testclass together?
Normally black box testing means that you cannot look at the implementation of the code under test. So your tests are based on the specifications or if there is not one, on your common sense.
cheers
Thomas

When making a function module, what is difference between test /unit test

best regards,

Hi,
ABAP Unit Tests
Structure of Unit Tests
An ABAP Unit test unit (TU) can be a class, function pool, executable program, or module pool. You can call ABAP Unit for testing individual TUs from the Class Builder (SE24), Function Builder (SE37), ABAP Editor (SE38), and SE80. Mass tests can be carried out from the Code Inspector.
You organize your tests into classes and then into test methods, which are all part of the TU. The system checks small units within the TU, hence the name ABAP Unit. The aim of a test method is to check whether a unit returns the desired result. For this purpose, there are methods of the service class CL_AUNIT_ASSERT that execute comparisons between target and actual values calculated by a unit. The results of all unit tests of a TU are then shown in the ABAP Unit result display.
Example
Let us look at an example to help clarify this. Our minimalist TU is a percentage calculator that delegates this task to a subroutine:
REPORT Percentages.
PARAMETERS: price TYPE p.
PERFORM minus_ten_percent CHANGING price.
WRITE price.
FORM minus_ten_percent CHANGING fprice TYPE p.
price = fprice * '0.9'.
ENDFORM.                    "Minus_ten_percent
We add a test class to the report, which tests whether the subroutine correctly calculates the percentage for a specific value.
CLASS test DEFINITION FOR TESTING. "#AU Risk_Level Harmless
"#AU Duration Short
PRIVATE SECTION.
    METHODS test_minus_ten_percent FOR TESTING.
ENDCLASS.
CLASS test IMPLEMENTATION.
METHOD test_minus_ten_percent.
    DATA: testprice type p value 200.
    PERFORM minus_ten_percent CHANGING testprice.
    cl_aunit_assert=>assert_equals( act = testprice exp = 180
                        msg = 'ninety percent not calculated correctly').
ENDMETHOD.
ENDCLASS.
The test class and the test method TEST_MINUS_TEN_PERCENT are recognized by the tool through the addition FOR TESTING. The additions "#AU RISK_LEVEL HARMLESS and "#AU DURATION SHORT are not optional comments but annotations containing required technical information. With RISK_LEVEL you specify to what extent, if at all, executing the test endangers critical data. The time is specified so that any tests in endless loops are automatically cancelled due to a timeout.
In the transaction SAUNIT_CLIENT_SETUP, you can make settings for an entire system with regard to the RISKLEVEL of tests and the times assigned to the individual attributes that specify the permitted duration (DURATION: SHORT, MEDIUM, and LONG). For example, in some development systems you will want to prohibit tests that change important data. If the test is cancelled for any reason, it is possible that some data may be left with invalid values or in an inconsistent state. Therefore, you will set the permitted RISKLEVEL suitably low in such systems.
Service of the Class CL_AUNIT_ASSERT
As parameters, the service method CL_AUNIT_ASSERT=>ASSERT_EQUALS requires a target value and an actual value, which is the result of the tested calculation; it then compares the two values. The MESSAGE parameter should contain a text that explains what went wrong during the test. You can also pass a parameter with the service method CL_AUNIT_ASSERT=>ASSERT_EQUALS that specifies the severity of the error, as well as a parameter stating how to proceed if the test fails: Should the test method simply continue, or should the current test method, the entire test class, or all tests of the TU be canceled?
In addition to this method, the class CL_AUNIT_ASSERT also provides other methods, which execute different checks and pass the results to the framework. Most importantly, you should note that you can use the parameters of the methods of the service class CL_AUNIT_ASSERT to control the flow of the whole unit test and include information in the test methods that will later provide you with important details about any errors in the result display.
ABAP Unit Result Display
On the left side of the result display, all the tests of your TU are grouped into a task. In our case, this is only one test class with a single method:
Via the name of the method, you can see what parts of the test method caused errors during the test:
The message you passed with the service method is displayed at the top. Below that, you can which values diverge and can navigate to the class via the stack line.
In our example, a closer examination of the code reveals that the input parameter of the report was confused with the change parameter of the subroutine.

Unit test and bug fixing

hai i m an abap devoloper i need to know how to fix a bug and how unit test is evaluated or how its done can u briefly explain me ,i know errors detactin thru debuggger then whats for unit test can u explain me this concept

Unit (Functional) TestingSAP Component or Feature Available
Services
   1. Unit (functional) testing
Unit Testing
   1. A process for verifying that software, a system, or a system component performs its intended functions.
   2. Unit transactions are tested against their own specifications and design documents.
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 separately 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.
Integration Testing
   1. An orderly progression of testing in which software elements, hardware elements or both are combined and tested until the entire system has been integrated.
   2. Integration tests deal mainly with the testing of cross-application process chains in addition to transactions and business processes. The process models and the test cases derived from these form the basis of these tests.

Unit Test Generator - VS 2008 (Cannot add oracle data source)

Hi All,
Okay this might just be me (new to ODT for VS) - but If I start VS, go Test -> Add Test.
Create a Database Unit Test.
[Give it some name]
write a query such as select * from <>
add a test checksum condition , and try to configure the checksum condition.. (Hit configure on the properties - under misc).
I go to new connection ...
I only have SQL Server (sqlClient) available. Is the unit test generator/validator something that oracle does not currently yet support?
(Yes the ODT 11i for VS 2008 is installed, can add a data connection to Oracle systems/query oracle in VS - just cannot add a Oracle database connection for unit database tests).
Or has anybody found a way to make this very useful piece of functionality work ?
Best Regards,
D

The same thing happens, If I go File -> Open -> Oracle Database Project Items -> SQL Script.
This comes up as disconnected.
When right click on the new script choose connect, only SQL Server provider is available with no ability to choose a oracle provider (greyed out to choose a diff connection provider).
Prehaps someone has seen this before?

Unit & Parallel testing

Similar Messages

Maybe you are looking for