Skip to main content

Static and Non-Static

 

What is the purpose of the static keyword in Java?

The static keyword is used to declare class-level variables and methods. They belong to the class rather than instances of the class and can be accessed using the class name.

can we use the static keyword for package level access?

In Java, the static keyword is not used for controlling access levels. The static keyword is primarily used to define class-level members, such as variables and methods, that are associated with the class itself rather than with instances of the class. The concept of access levels, on the other hand, is controlled by access modifiers.

public class MyClass {

    public static int publicStaticVariable = 10;

    static int packagePrivateStaticVariable = 20; // package-private by default

    private static int privateStaticVariable = 30;

}

To summarize, while static is used to define class-level members, access modifiers (public, protected, default, private) are used to control the visibility and accessibility of those members. The use of static and access modifiers is independent of each other.

It's important to note that while static members have their use cases, they should be used judiciously, as overuse of static members can lead to code that is tightly coupled and less maintainable. Instance-specific members (non-static) are more common in object-oriented programming, where each object has its state and behavior.

does instance of the classes are non-static?

Instances of a class are non-static. When we create objects (instances) of a class in Java, each object has its own set of instance variables and instance methods. These are attributes and behaviour’s that are specific to each individual object.

Comments

Popular posts from this blog

Had you to design test cases for a complex feature. What factors did Tester consider, and how did prioritize test scenarios?

  Take an instance as new application has integrated into existing applications(i,e., Running on real time )Customer want to integrate their application into third party vendors in order to let the customer order their needs through our created app itself. Factors Consisdered : Error Handling , Functional Requirements , Edge cases , Non-Functional Parameters . Transaction Flow Flow1: Customer Land on third party vendors app and start picking their items. Flow2 : Picked Items has to go Cart Page and can see number of items added by visually. Flow3: Once click to checkout , it will allow the user to input their card details and processing transaction. Flow4:Once Transactions done, newly created app show the details of the order and online tracking number . Prioritize scenerios based on the Business Emergency and needs ,well in briefly communicate to team members to identify the Critical paths and prioritize the that test suite first and Start  the execution based on what need to...

Pre conditions and Post conditions in Test Ng.

Pre conditions and PostConditions in Test Ng. Vision of Preconditions and Postconditions: 👉 Ensuring Test Isolation: By using preconditions and postconditions, you ensure that each test method is executed in isolation, with a clean and consistent state. 👉Promoting Reusability: Setup and teardown tasks defined in preconditions and postconditions can be reused across multiple test methods, promoting code reuse and reducing redundancy. 👉Maintainability: Clearly defined preconditions and postconditions enhance the maintainability of test code. Changes or additions to the setup and cleanup logic can be made centrally in these annotated methods. TestNG PreConditions and PostConditions flow.   Before Suite (once) Before Test (once for each <test> in the suite) Before Class (once for each class with test methods in the <test> ) Before Method (before each test method) Test method execution After Method (after each test method) After Class (after all test methods in ...