Selenium/Java POI：执行SignIn_Action时ActionKeywords.input抛空指针，driver写法正常

Let’s break down why you’re hitting that NullPointerException (NPE) when using ActionKeywords.input("txtbx_UserName", sUserName1)—especially since your direct Selenium call works perfectly. Here are the most likely culprits and step-by-step ways to debug them:

1. Missing or null WebDriver reference in ActionKeywords #

Your working direct call uses a valid driver instance, but the ActionKeywords class might not have access to this same active instance. Common scenarios:

• The driver variable in ActionKeywords is static but never initialized with your test’s running WebDriver instance.
• It’s an instance variable, but you’re using an uninitialized ActionKeywords object (or one that wasn’t passed the valid driver).

How to verify:
Add a debug print statement at the start of the input() method:

System.out.println("Driver reference in ActionKeywords: " + driver);

If this outputs null, you need to ensure ActionKeywords receives your test’s active driver before calling input()—either via a constructor, setter method, or updating the static variable.

2. Null objMap reference in ActionKeywords #

In your working code, objMap.getbjectLocator("txtbx_UserName") returns a valid locator, but inside ActionKeywords, the objMap itself might be null. This could happen if:

• ActionKeywords doesn’t initialize objMap (it’s declared but never assigned to your actual object map instance).
• You’re passing a different, uninitialized objMap to ActionKeywords.

How to check:
Add these print statements in the input() method:

System.out.println("Object Map in ActionKeywords: " + objMap);
System.out.println("Fetched locator: " + objMap.getbjectLocator("txtbx_UserName"));

If objMap is null, you’ll need to ensure ActionKeywords uses the same valid objMap instance that works in your direct call.

3. Static vs. Instance Scope Mismatch #

If ActionKeywords relies on static variables for driver or objMap, but your test creates new instances of these objects, the static references might stay null. Your direct call uses the instance from your test class (which is valid), but ActionKeywords isn’t synced up.

How to fix:

• If using static variables, update them with your test’s active driver/objMap before calling input().
• Or, switch ActionKeywords to use instance variables, and initialize an ActionKeywords object with your driver and objMap at the start of your test.

Quick Summary #

Since your direct Selenium call works, the locator itself is valid, and your driver/objMap are in good shape there. The problem is definitely that ActionKeywords isn’t getting a valid reference to either driver or objMap when you call input(). Start by logging those two objects at the start of the input() method—this will immediately point you to the null culprit.

内容的提问来源于stack exchange，提问作者Rahul