This is a keyword and used as reference to Current object address in java. 

It means by using which object the method is called that object hashcode is stored inside the 'this'.

bcoz the static method does not contains the 'this' reference.

Non-static member class is a class defined inside outer class with out static modifier.

EX:

class A { // top level class or outer class

    ......

    class B { //non-static member class

    }

    .....

}

Static member class is a class defined inside outer class with static modifier.

EX:

Class A {  //top level class or outer class

    .....

    static class B {  //static member class

    }

   .....

}

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc.  

In GUI testing, need to cover the customer requirement if don't have to validate  Font size, colors, spellings(labels) etc.

Every application should follow Microsoft rules like

- Controls should be Initcap (i.e every label should start with Capital letter )Can observe that in Win applications every label starts with Caps

- OK or Cancel button should exist

- Controls should not be overlapped

- Controls should be alligned properly (left side alignment is mandatory but the right side is optional)

- Controls should be visible

- Short cut keys should be provided

- System menu should exist (i.e if u press Alt key + Space bar a menu will appear at the left most corner )

- Mouse pointer events 

Colors, Label Names, Tab Order, Alignment, graphs , Navigation of the software to test in GUI Testing.

1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc.