I strongly urge you to follow the guide given by Jake in that post and to browse through these forums for the knowledge and information they contain.
I would also recommend that you stop using txting which is a very un-professional way of expressing yourself.
The scope of "any banking" application is humongous, if you have been requested to smoke test a build on a project you are working on and are not sure of what is expected you would be best discussing this with your test lead to determine exactly what is expected for smoke testing at the company and on the project you are working.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
Besides doing what Lynne suggested, you may want to check for appropriate behaviors of user interface controls (i.e., textbox, pull-down list, radio button, etc.). Check for the existence of UI controls on each page, window or dialog box; checking if the default state (such as enable, disable, highligthed, etc.) is as intended; checking if the default value or selected mode is as intended; checking if the tab order is as intended; and if the behavior of shortcuts (e.g., Ctrl-X, Ctrl-V, etc.) and other access keys (e.g., Alt-O for Open) is as intended.
Also check links, basic controls, such as backward and forward navigating, zoom-in and zoom-out.
one of the factor you have to consider is Margin, where developers always do mistakes while coding and mostly if it is an ATMs based project we have to take more care in accounting the account updating info...