ExcelUtil | Util package for importing and exporting Excel | Application Framework library

You can have check of Cell_Type before getting the cell value.

As @razvans points out, the error message here is great.

You're initializing your object with input_file_path: nil, and then inside of call you're checking if @input_file_path (set to input_file_path in the initializer, AKA nil) ends with a string.

There is no .end_with? method on nil. That's causing the NoMethodError error.

You could guard against nil in your end_with? call, or give it a default value in the initializer.

I see on swagger that request is POST, not Get, so you should change the how to setup API call: change queryParam --> post body. Read more: https://github.com/rest-assured/rest-assured/wiki/Usage#request-body. Example:

The null pointer exception happens in your own code. You haven't provided the full source code, nor the excel file (or described how many rows and columns it has from the start), so I can't say what exactly it is that is null. But you can just look at your code at line 65 of ExcelUtility.java.

But just looking at the javadoc, there are a few candidates. For one, the workSheet object might be null, since workBook.getSheet(SheetName) returns null if there is no sheet named "MainTable". Otherwise, workSheet.getRow(RowNum) can still result in a null value, if there is no such row. And remember that the row is zero-based, so when you ask for row "4" it is actually the 5th row you are asking for. Does your excel file have five rows in this sheet?

If this is not the problem, then try to use the debugger of the IDE you are using, and put a breakpoint at the first line inside the method "setCellData" (ie, put a breakpoint on row = workSheet.getRow(RowNum);) then use the debugger to see the actual value of all the variables. Find the object that is causing the Null Pointer Exception, then trace the code backwards until you find why it is null. If you can't get your debugger to work, you can just add some simple System.out.println("variable: " + variable") at different places in your code, so that you can see the values when the code runs.

If nothing of this helps you find the problem, please post the full source code (including imports), with line numbers matching the one in your code. And a screenshot of your excel file, with the "MainTable" sheet open would help too.

You're using the wrong XlFileFormat member for the format you want when you save the file.

According the documentation:

• xlWorkbookNormal is for *.xls files.
• xlWorkbookDefault is for *.xlsx files.

Pass Excel.XlFileFormat.xlWorkbookDefault instead.

An error occurs due to test data that does not match with the test method parameter.

A solution to your problem:

The error occurs because there are defined names in the workbook that refer to a sheet/table/range that no longer exists. Referenced from here

First I was able to duplicate your error. Second, I deleted these Names and your code worked fine.

Unfortunately, the exception happens anytime you reference the workbook so I see no clear way to solve this outside the package.

Try using dependsOn or use a priority in your test annotations. @Test methods are not always executed in the same order as they are written. Also if the Tests are run in parallel this would be an issue as well. Since logOut is completely dependent on the login method, try using

abq_ExcelUtilities doesn't seem to have an auto save option. If exporting data is of your main concern, you could do it without the need of abq_ExcelUtilities.

xydata_object = session.xyDataObjects[xyCurveName]
session.writeXYReport(fileName=*.dat, appendMode=OFF, xyData=(xyCurveName))

Look into session.writeXYReport in the abaqus python scripting reference documentation for more information.