Similar Questions

• Error in Unit Test Framework: "the path of the VI test is not valid."

  I get this error on files lvtest for a few screws, it appears so when I click on the button "import values of VI.  The unit test framework correctly on some screws, but some work raise the error.  I tried to move and rename the files and of coarse checked the path of the file.  I'm open to suggestions, I'm starting to like what the Unit Test Framework is capable of, but this error becomes a problem for me.

  Thank you

  John

  Hi John,.

  It seems that I do not receive the same error as you.  In the Advanced tab of .lvtest files, that you selected as the Configuration setting?  If you left it as default value, can you check to see if the orders/lights are selected in the connector pane?

• Automation of unit tests for the development of the ATG

  Hello
  I'm trying to set up unit tests automated to ATG. Is there anyone who has had success with this? I searched the whole forum and there is no indication in this sense. Is there anyone doing TDD for ATG?
  
  I've tried the ATG dust, but it is not useful and has many gaps. Anyone succeeded with other frameworks such as Mockito, needle, EasyMock etc. ? Any help is appreciated.
  
  It will be interesting to know what the ATG developers use for unit tests.
  
  Thank you.

  You can try Mockito.

  Setup
  1 initialize the component to be tested (Formhandler/repository/droplet etc.) and possible data (form entries etc.).
  2 mock, the calls of the method required when using method in mockito.

  Test
  1. write all possible test methods.
  2 when use, check the methods in Mockito for testing your methods.
  3. you can also use assertions to test the results (Ex: form errors)

• How can manage us versioning of unit tests in the Test Oracle Manager

  Hello
  
  Usually, we have several versions of our product. How to manage versions of testcases in Oracle Test Manager (MTM) so that we can run a version-specific unit tests? Any ideas?
  
  Thank you

  Hello

  You can create a separate test group to organize unit tests by version. You can also choose the tests that will be run using the Scheduler. Or you can create a separate project to store your unit tests by app version/version. You can't store different versions of a script automated in a unit test in OTM.

  Concerning

  Rajesh

• Creating text file use new file, by returning the result by completely removing the lines of code to extend script?

  Hi guys

  Creating new files .txt in extendscript thru new file returns results by removing all the code in extend script.

  Example of

  -------------------

  var fPerCode = 'hack ';

  var myFileP = new File($.fileName);

  var myFilePtS = myFileP.parent.fsName.toString ();

  myFileP.open ('w');

  myFileP.write (fPerCode);

  myFileP.copy(myFilePtS+"\\"+"Mytools_icons"+"\\"+"name.txt");

  myFileP.close ();

  Alert ("path to the fullper.bat file" + "\n"+myFilePtS+"\\"+"Mytools_icons"+"\\"+"name.txt");

  If you run the above code, you see the result by disabling all of the code above.

  can someone help with this problem?

  You have a problem that you are writing your own script file and then doing a copy...

  You also toString() of unnecesery and deformities (+).

  Here is a fix your code:

  var fPerCode = 'hack ';

  var myFileP = new File($.fileName);

  var myFilePtS = myFileP.parent.fsName;

  var myNewFile = new File (myFilePtS + "\\Mytools_icons\\name.txt");

  myNewFile.open ('w');

  myNewFile.write (fPerCode);

  myNewFile.close ();

  Alert ("path to fullper.bat file\n" + myNewFile.fsName);

• Run the .bat file using fileObj.execute () showing the result by completely removing the lines of code in extend script?

  Hi guys

  I created a dynamic .bat file created inside java and copy it to a location and managed through fileObj.execute ();

  Example of

  -------------------

  var line1 = 'some code ";

  var line2 = 'some code ";

  myCode var = line 1 + line 2;

  
  

  var myFileC = new file

  myFileC.open ('w');

  myFileC.write (myCode);

  myFileC.copy ("some location\file.bat");

  myFileC.close ();

  Run the .bat file

  batFile var = new file ("of the location\file.bat");

  batFile.execute ();

  Now .bat file is successfully executed but the content of this file created bat shows up to extend in script by removing all my code above...

  I have to cancel to do back whenever I run and sometimes accidentally I saved it lose all the code.

  can someone help with this problem?

  Simply change it to this:

  var myFileC = new File ("some location\file.bat");

  myFileC.open ('w');

  myFileC.write (myCode);

  myFileC.close ();

• Unit test: calculation of the length of the different columns in recordsets provided and received led to false a test failure

  Dear team of SQL Developer,

  It seems that the calculation of the length of the column in the expected and received recordsets behaves differently in some cases (when stored proc variables are used in the generation of the REF CURSOR, despite the explicit definition of the type of record): the length of the header and the length of the value in the set of records received are truncated to arbitrary length based on the returned value which leads to a false failure of a unit test. I.e. registries are the same in both sets of records, but the test run fails to the comparison of the recordsets because of different length. Please see the screenshot below:

  

  Here's the test case if you need to reproduce the problem/bug in your environment:

  1. use the default schema of HR of the Oracle examples package that comes with an 11 g database.

  2. change the HR. Table EMPLOYEES with the addition of a new column VARCHAR2 (4000) LONG_LAST_NAME:

  ALTER TABLE HR. EMPLOYEES

  ADD (LONG_LAST_NAME VARCHAR2 (4000));

  Update hr.employees set long_last_name = last_name;

  commit;

  3. create a PKG_TEST2 package with the source code below in the HR schema:

  ----------------------------------------------------------------------------------------------------------------------

  create or replace PACKAGE PKG_TEST2 AS

  TYPE EmployeeInfoRec IS RECORD

  (

  long_last_name employees.long_last_name%TYPE,

  first name employees.first_name%TYPE,

  E-mail employees.email%TYPE

  );

  TYPE EmployeeInfoRecCur IS REF CURSOR RETURN EmployeeInfoRec;

  FUNCTION getEmployeeInfo (p_Emp_Id employees.employee_id%TYPE)

  RETURN EmployeeInfoRecCur;

  END PKG_TEST2;

  ----------------------------------------------------------------------------------------------------------------------

  CREATE OR REPLACE PACKAGE BODY PKG_TEST2 AS

  FUNCTION getEmployeeInfo (p_Emp_Id employees.employee_id%TYPE)

  RETURN EmployeeInfoRecCur AS

  v_EmployeeInfoRecCur EmployeeInfoRecCur;

  v_LongLastName varchar2 (4000);

  BEGIN

  Select long_last_name from v_LongLastName

  employees

  where employee_id = p_Emp_Id;

  --

  OPEN FOR V_EmployeeInfoRecCur

  V_LongLastName SELECT long_last_name,

  first name,

  E-mail

  This_is_very_long_table_alias employees

  WHERE employee_id = p_Emp_Id

  order by 1 CSA;

  --

  RETURN v_EmployeeInfoRecCur;

  EXCEPTION

  WHILE OTHERS THEN

  LIFT;

  END getEmployeeInfo;

  END PKG_TEST2;

  
  

  ----------------------------------------------------------------------------------------------------------------------

  4. create a unit test for the PKG_TEST2.getEmployeeInfo stored procedure: (click the command create Test, select the stored procedure, click Ok for the pop-up message, click Next, click Finish).

  5. update the default value of dynamic query of value with the one below and save/post changes.

  Select the cursor)

  SELECT long_last_name,

  first name,

  E-mail

  Employees

  WHERE employee_id = idqry.employee_id

  order of the 1 CAD

  ) RETURNS $,.

  idqry.employee_id as P_EMP_ID

  from (select employee_id

  employees

  where rownum < = 5) idqry

  6. run the unit test newly created in the debug mode to display the shot.

  Thus, the record type 'EmployeeInfoRec' in the package clearly defines the LONG_LAST_NAME as VARCHAR2 (4000) through reference for the data type of column in the referenced table.

  But for some reason, the SQL Developer does not calculate correctly its length in the recordset "Receipts" If a variable is used (could be one as variable simple varchar2 in this reproducible test or complex variable of type of the object).

  Any ideas on that? Looks like another bug...

  Thank you

  Val

  The bug has been reproduced by the SRB and documented within the system of Support of Oracle SQL Developer team to pick it up:

  Bug 19943948 - TEST UNIT RETURNS EXPECTED ERROR: [LONG_LAST_NAME

  Hope the bug name can later be changed to something more descriptive, but it is not really... my only concern is the speed at which the known bugs would be fixed...

  Thank you

  Val

• PL/SQL, used in application of the APEX of unit tests

  question by my client:

  I develop an Oracle Application Express application and work on unit tests for stored procedures in PL/SQL and the packages that are stored in the underlying database and used by the application of the APEX. These unit tests must run in the context of SQL Developer Unit Test.
  The problem is that the PL/SQL code stored in the database using functions such as NV('APPLICATION_ITEM') to access items in the application of the apex. They do return all values when I try to execute the PL/SQL within the unit test framework, that is to say in the backend. While it is good that the NV is not error, NULL haven't really work well in my scenario either (for example when the result of this function is inserted into a column NOT NULL in a table). I can think of a few workarounds, such as the creation of my own function NV within the schema to test return values desirable, but nothing seems a really satisfactory solution. I wonder if there is no recommendation to Oracle for this scenario - how can I run code that uses the APEX via backend-specific features. I found nothing in the documentation of the APEX for this but I would like to know if there is a recommendation how to better deal with this case.
  
  I use SQL Developer version 4.0.0.13.80

  Hello

  Indeed, you must set your PL/SQL function calls. This would be the cleanest solution.

  There is an alternative. Please see the following article on the creation of an APEX in PL/SQL session: Martin Giffy D'Souza on Oracle APEX: how to create a Session of the APEX in PL/SQL

  This approach allows to set the values of APEX application item before you run your unit tests. I don't know if it's possible in SQL Developer Unit Test, but it might get you further down the road.

  Good luck

  Nick

• renaming of unit test

  After the discussion here:

  http://forums.NI.com/T5/LabVIEW/cannot-rename-lvtest-file/m-p/2621909/highlight/true#M785332

  I eventually create several dummy unit tests in the lvproj then exit and restart labview and then correctly configure these dummy unit with own names test.

  What is the Unit Test framework in $$? Pretty boring we can if expect a simple rename the feature to $$.

  Has anyone found alternative workaround in the meantime?

  Hello

  the expected way to create tests is not by right click on "my computer"...

  Here's the official help file:

  Creating Tests (Unit Test Framework Toolkit)

  By creating the unit test of the VI the name change should be no problem!

  Best,

  Anna

• Unit test: behavior another header in recordsets provided and received led to false a test failure

  Dear team of SQL Developer,

  It seems that the headers in the expected and received Recordset behaves differently: the headers of expression in the expected Recordset are truncated to 30 characters and the same expression in the set of records received headers are not truncated, which leads to a false failure of a unit test. That is that the records are the same in both sets of records, but the test run fails to comparison of sets of records due to the different headings. Please see the screenshot below:

  

  Here's the test case if you need to reproduce the problem/bug in your environment:

  1. use the default schema of HR of the Oracle examples package that comes with an 11 g database.

  2 create a PKG_TEST package with the source code below in the HR schema:

  ----------------------------------------------------------------------------------------------------------------------

  create or replace PACKAGE PKG_TEST AS

  TYPE EmployeeInfoRec IS RECORD

  (

  employees.last_name%type last_name,

  first name employees.first_name%TYPE,

  E-mail employees.email%TYPE

  );

  TYPE EmployeeInfoRecCur IS REF CURSOR RETURN EmployeeInfoRec;

  FUNCTION upperCaseLastName (p_Last_Name employees.last_name%TYPE)

  RETURN varchar2;

  FUNCTION getEmployeeInfo (p_Emp_Id employees.employee_id%TYPE)

  RETURN EmployeeInfoRecCur;

  END PKG_TEST;

  ----------------------------------------------------------------------------------------------------------------------

  CREATE OR REPLACE PACKAGE BODY PKG_TEST AS

  FUNCTION upperCaseLastName (p_Last_Name employees.last_name%TYPE)

  RETURN varchar2 AS

  BEGIN

  RETURN upper (p_Last_Name);

  END upperCaseLastName;

  FUNCTION getEmployeeInfo (p_Emp_Id employees.employee_id%TYPE)

  RETURN EmployeeInfoRecCur AS

  v_EmployeeInfoRecCur EmployeeInfoRecCur;

  BEGIN

  OPEN FOR V_EmployeeInfoRecCur

  SELECT upperCaseLastName (last_name),

  first name,

  E-mail

  This_is_very_long_table_alias employees

  WHERE employee_id = p_Emp_Id

  order by 1 CSA;

  --

  RETURN v_EmployeeInfoRecCur;

  EXCEPTION

  WHILE OTHERS THEN

  LIFT;

  END getEmployeeInfo;

  END PKG_TEST;

  ----------------------------------------------------------------------------------------------------------------------

  3. create a unit test for the PKG_TEST.getEmployeeInfo stored procedure: (click the command create test, select the stored procedure, click Ok for the pop-up message, click Finish).

  4. update the default value with the following dynamic query and save the changes.

  Select the cursor)

  SELECT pkg_test.upperCaseLastName (last_name),

  first name,

  E-mail

  This_is_very_long_table_alias employees

  WHERE employee_id = idqry.employee_id

  order of the 1 CAD

  ) RETURNS $,.

  idqry.employee_id as P_EMP_ID

  from (select employee_id

  employees

  where rownum < = 5) idqry

  5. run the unit test newly created in the debug mode to display the shot.

  The work around is to use an alias for the expression of long short, but our code is in Production, and we do not a new version whenever soon to add aliases... but we plan to use SQL Developer to automate our unit of PL/SQL code, tests once we clearly have some of the problems with the tool, we know...

  Please advise...

  Thank you

  Val

  Of course, Jeff... CS it logged as a bug... could be changed to apply for development later, I guess...

  BUG 19826375 - header BEHAVIOR IN the GAMES of RECORDS EXPECTED/RECEIVED LED to the ERROR

  Thank you

  Val

• View of unit test does not appear

  Hello, I have followed this tutorial on configuring SQL * Developer for unit tests: http://www.Oracle.com/WebFolder/technetwork/tutorials/OBE/DB/sqldev/R30/sqldev_unit_test/sqldev_unit_test_otn.htm#T4 the fist step under "create a Unit Test" says ' select view > Unit Test ' However the view of unit test never appears. Is there something else I should do to get this point across to appear? I'm on Windows 7 x 64 using Sql * developer 4.0.2.15 build 15.21 x 64. Thank you,-joel

  Looks like you have to get rid of that other install and stick with a new...

• Unit Testing Unit Test Framework when the expected production is just a table of NaNs to report a fake PASS

  It is a cross-post of the Unit Testing Group:

  https://decibel.NI.com/content/message/121915#121915

  I remember having this problem with the old version of the unit testing framework, but alas, it is still present in the new version.

  To do this, I use LabVIEW 2015.

  A customer contacted ask me what to do, because the expected output was table of NaNs and the VI under test returns an array of numbers and yet, the test was passing!

  My suggestion to use as a solution was to create a defined trial user who would test for the table of NaNs. I was wondering if someone here had found this problem and if you have further suggestions other than user defined Test.

  Until someone suggests we turn to JKI VI tester for this project, I can tell you that we use UTF and tester of JKI VI not because the client is in a regulated industry.

  A video describing the problem and the workaround (via user defined Tests) is here: https://youtu.be/AoBe-Gw2Nzo

  Question: Is using a user defined Test is the best approach? We missing something in the way that the Unit Test is defined which translates the fake of the Test infrastructure Unit reports that the test successful?

  Thank you

  Fab

  Hey Fab,

  I was able to reproduce the problem on my machine and I have observed the same results. What I see in the video, it looks that you are setting the unit test. I think that this is a bug rather than your test configuration, so I presented a report on this issue will have to be reviewed by the R & D.

  Go ahead, I agree that a user defined Test is the best solution in this case. If it meets the needs of your clients, I recommend you take this option.

• Distribution of the source - unit test dependency problem

  Hello

  I developed and API and I want to make the distribution of the sources, however my faulty build (error message is below) due to the error of reclassification of the Unit Test framework that I use to test my code. All Unit Tests are in the same folder, called "UnitTests", which is a part of a class. If I delete the UnitTests from the class folder, source distribution is created as expected. I try to put the folder always excluded UnitTests, but it does not help.

  I use LV 2012.

  Any ideas what I am doing wrong?

  Thank you

  Andrej

  Error message:

  LabVIEW does not find a file that is a dependency of a startup, exported or always included VI.

  File not found: the file "C:\Program Files (x 86) \National 2012\vi.lib\utf\dialogs\utf_defocus_trees.vi" must have the qualified name of "NI_UnitTestFramework.lvlib:utf_defocus_trees.vi", but it has the qualified name of "utf_defocus_trees.vi".

  The missing file can be referenced by one of the libraries included in the compilation or the file - CircularBuffer.lvlib. To resolve this problem:

  -Open all the startups, exported or always included live, recompile them (CTRL-SHIFT click the Run arrow) and keep them to update their dependencies.
  -Open libraries included in the building and check the existence and the location of the referenced files. Also, try building with the option of additional exclusion, 'Delete unused library of the project members', verified.

  Is attached to a fixed version of utf_defocus_trees.vi.  Place it in your \LabVIEW 2012\vi.lib\utf\dialogs directory .

  In addition, you might want to load/save utf_test_properties_sub.vi to get rid of the dirty dot.  This VI is located in the: \LabVIEW 2012\resource\framework\providers\utf.

• How calculated the code coverage in unit test infrastructure

  I'm looking for documentation on how the unit test framework calculates code coverage.

  I just recently installed the unit test framework and I had mixed results with the code coverage feature.  I manually calculated all the branch points in my vi, but the framework calculates more that I can think of, which gives a value of code coverage less than stellar (51%).  Is there documentation for how it is calculated?  I'm either missing something fundamental, or there is a bug with the framework.

  My vi consists of a loop (with shift registers) uninitialized which runs once.  On the inside of the loop is a business T/F structure that leads to a listed case structure possible two cases (one of which is the default value)... pretty basic.  Inside one of the structures is a loop and the other is cross.  For some reason, the unit test framework calculates 7 "flags chart run.  I use the method of "external" test harness to call all my test cases for the vi under test, b/c frankly it was easier to use than the UI provided.  I don't know if this is the cause, b/c I saw the other oddities when using it, which I'll save for another thread of discussion.

  Code coverage is calculated by dividing the number of diagrams, code that was executed by the number of diagrams in your VI altogether. Each VI has at least 1 schema (schema-block real). Loops have a single diagram each, case structures and sequences have a single diagram by image and so forth (=> from your description, your VI has at least 7 diagrams). You can double-click the patterns that were not executed in the Unit Test Framework results dialog box to be displayed.

  This approach does not reflect the amount or complexity of the code that contains each diagram. We looked at various ways of counting nodes, terminals, controls, son and other, that would give you a number that reflects your code with more precision. Unfortunately, neither of these approaches gives values that can easily be understood without some knowledge about the inner workings of LabVIEW. We chose to go with a solution that is completely transparent to end users.

  Thank you

  Herbert

• VI test a string control configured to view password, it displays 'normal view' mode in the Unit Test Framework lvtest Properties dialog box

  Configuration of the password does not lvtest UTF Properties dialog window. It's probably a bug.

  Hey jorgeinSD,

  The Unit Test is designed to test the input values and compare them with a desired output value to make sure that your VI works under different entries. For this reason, it is necessary that the user makes tests see the entry and not just values «*» Your VI should not change (as in the VI should still display mode password, ' * '), but the properties of Unit Test should display the actual value and not mode password. Is that what you mean by 'configuration of the password does not UTF' or did, I misunderstood the question? I hope this helps!

  -Nathan H