Understanding Static in Java: How Instantiating the Same Class Affects Driver Initialization

Dive into the core of Java's static fields and understand how class instances share variable states. Learn why your driver isn't null even if it's not initialized in every instance.
---
This video is based on the question https://stackoverflow.com/q/67238867/ asked by the user 'Wizard' ( https://stackoverflow.com/u/10276728/ ) and on the answer https://stackoverflow.com/a/67239064/ provided by the user 'hfontanez' ( https://stackoverflow.com/u/2851311/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Instantiating the same class from different classes

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding Static in Java: How Instantiating the Same Class Affects Driver Initialization

Java is a powerful language commonly used for mobile application testing with frameworks like Selenium and Appium. A common question developers face is around the use of static variables in class instances, particularly when dealing with initialization of objects such as AppiumDriver. Let's break this down to understand why your driver might not be null even if you haven't explicitly initialized it in every instance of its class.

The Problem at Hand

In the scenario you're facing, you have a BaseTest class where you initialize an AppiumDriver object. You then create instances of this class in other classes like LogInTest and LoginPage. The confusion arises because you are not calling the initializeDriver method in the LoginPage, yet you're questioning why the driver is not null. Understanding this boils down to the significance of the static keyword in Java.

Static Variables in Java

What Does Static Mean?

When a variable is marked as static, it means that this variable is shared among all instances of that class. In other words, regardless of how many objects you create from this class, they all refer to the same variable in memory.

Example from Your Code

In your BaseTest class, you have the following snippet:

[[See Video to Reveal this Text or Code Snippet]]

This means that all instances of BaseTest share the same driver variable. So, if any instance sets the driver, that value is reflected across all other instances.

How Does This Affect Your Test Classes?

Consider the following scenario between LogInTest and LoginPage:

LogInTest creates an instance of BaseTest and calls initializeDriver, thereby setting the shared driver variable.

LoginPage creates another instance of BaseTest but does not call initializeDriver. However, since driver is static, it still references the initialized driver that LogInTest set.

Key Takeaways

Shared State: When you create a static variable, it creates a shared resource amongst all instances of that class. In this case, the AppiumDriver is shared.

Null Pointer Risk: If you attempt to access the driver from an instance of BaseTest without initializing it first (i.e., if initializeDriver was never called in that context), you risk encountering a NullPointerException. This is because you would be trying to work with a null reference.

Execution Order and Annotations

The second aspect that plays a crucial role here is the order in which methods are called during testing. In your code, you have the @ BeforeClass annotation used in LogInTest:

[[See Video to Reveal this Text or Code Snippet]]

This annotation ensures that initializeDriver is executed before any tests run, effectively setting the driver before it is used in the tests that follow. This is why even when you create a new instance of BaseTest in LoginPage, the AppiumDriver is indeed not null if it has been initialized previously in LogInTest.

Conclusion

In summary, your understanding of the situation is clarified by recognizing the implications of static fields in Java. The shared driver variable across instances allows classes like LogInTest and LoginPage to interact with the same AppiumDriver object, despite the fact that not all of them initialize the driver directly. This powerful feature of Java can help manage shared resources efficiently, but it requires a careful approach to avoid errors like NullPointerException.

Understanding these nuances will greatly enhance your testing strategies and reliability in future mobile testing endeavors. Happy coding!