Animals in the Stock Market

BULLS:

An investor who thinks the market, a specific security or an industry will rise. Investors who takes a bull approach will purchase securities under the assumption that they can be sold later at a higher price.  




BEARS

An investor who believes that a particular security or market is headed downward. Bears attempt to profit from a decline in prices. Bears are generally pessimistic about the state of a given market.

"A bear swipes down with its paws where a bull thrusts upwards with its horns"



STAGS:




A stag would be equivalent to a day trader who attempts to profit off short-term market moves by quickly moving in and out of positions.









CHICKENS:




This refers to individuals who are fearful of the stock market and stay away. Their fear overrides their need to make profits so they stick to conservative instruments such as bonds, bank deposits or company deposits. Their risk tolerance in investment terms is very low.






PIGS:

“Bulls make money, bears make money, pigs get slaughtered” is an old saying that cautions against excessive greed and impatience. 

Pigs willing to take a high risk, invest based on hot tips and want to make a quick buck in a hurry. These are the ones who burn their fingers and lose money in the market. 

WOLVES:





The animal has been employed as an analogy to powerful individuals who could employ criminal or unethical means to make money. Such rapacious or ferocious individuals are behind scams that jolt the market when it comes to light.





OSTRICHES:





 Investors who stick their heads in the sand during bad markets hoping that their portfolio is not severely hit.

Smoke and Sanity Testing

Usually we perform Smoke/Sanity testing once we got any new build for testing. Both sanity tests and smoke tests are ways to avoid wasting time/ effort by quickly determining whether an application is too flawed to merit any rigorous testing.

Smoke Testing:

Reason for this name: In electronics and electrical engineering once we create an electronic circuit they connect to power, which will sometimes produce actual smoke if a design or wiring mistake has been made.

Objective of smoke testing: Smoke Testing is performed after software build to ascertain that the critical functionalities of the program is working fine. It is executed "before" any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application, so that the QA team does not waste time installing and testing the software application.

In Smoke Testing, the test cases chosen cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionalities of the system is working fine.

For Example a typical smoke test would be – Verify that the application launches successfully, Check whether all the GUI field are present in the application ... etc.

Sanity Testing:

Reason for this name: No idea on how they derived this name J

Objective of sanity testing: After receiving a software build, with minor changes in code, or functionality, Sanity testing is performed to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.

The objective is "not" to verify thoroughly the new functionality, but to determine that the developer has applied some rationality (sanity) while producing the software.

For Example, the Hello world programs often used as a sanity test for a development environment. If Hello World fails to compile the basic environment has a configuration problem.

DIFFERENCE BETWEEN SMOKE AND SANITY TESTING:

S.No	Smoke Testing	Sanity Testing
1	Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine	Sanity Testing is done to check the new functionality / bugs have been fixed
2	The objective of this testing is to verify the "stability" of the system in order to proceed with more rigorous testing	The objective of the testing is to verify the "rationality" of the system in order to proceed with more rigorous testing
3	This testing is performed by the developers or testers	Sanity testing is usually performed by testers
4	Smoke testing is usually documented or scripted	Sanity testing is usually not documented and is unscripted
5	Smoke testing is a subset of Regression testing	Sanity testing is a subset of Acceptance testing
6	Smoke testing exercises the entire system from end to end. Smoke test is designed to touch every part of the application in a cursory way.	Sanity testing is used to determine a small section of the application is still working after a minor change.
7	Smoke testing is a breadth first Approach	Sanity testing is a depth first Approach.
8	Smoke testing performed on a particular build is also known as a build verification test.	Sanity Testing is also called tester acceptance testing.
9	Smoke testing is like General Health Check Up	Sanity Testing is like specialized health check up

DIFFERENT TYPES OF ORDERS

ORDER:

An instruction, especially to a broker, to buy, sell, or conduct some other transaction involving Equity, FX, Commodity, etc,..

(A)              Time Conditions

Day Order: This order remains valid during the trading day at the end of which it is cancelled.

IOC: An Immediate or Cancel (IOC) order allows the user to buy or sell a security as soon as the order is released into the system. IOC order results into a trade if matched immediately with the counter order else it is cancelled. Partial match is possible for the order, and the unmatched portion of the order is cancelled. For example, if a buy order for 1000 Microsoft is received by the system and the sell orders for Microsoft is only for

500 shares in the system, the 500 shares will be bought and the balance buy order for 500 shares will be cancelled immediately.

Good-till-date: These orders stay open till a defined date after which they are cancelled if not executed.

Good-till-cancelled: These orders stay open till the client cancels it. Normally, the broker rechecks for validity of these orders with the client at periodic intervals.

(B)              Quantity Conditions

DQ: An order with a Disclosed Quantity (DQ) allows the user to disclose only a portion of the order quantity to the market. For example, if the order quantity is 10,000 and the disclosed quantity is 2,000, then only 2,000 is released to the market. After this quantity is fully matched, a subsequent quantity of 2,000 is disclosed. Thus, totally five disclosures with the same order number are shown one after the other in the market.

Fill-or-Kill: Here the order must be executed immediately and fully; else it has to be cancelled. Here partial execution of orders as in the case of IOC is not allowed.

All-or-none: Given some time constraints such as day, the entire order has to be executed or the client is not obliged to accept a partial execution.

(C)              Price Conditions

Market: Market orders are orders for executing the trade at the going market price. The buy order is matched with the quotes available on the offer side and vice versa as soon as the order is received. Here there is no restriction on the price at which the trade should be executed.

Limit: This order type places a limit on the price at which the trade can be executed. In case of a ‘buy’, the limit specifies the maximum price that the client is willing to pay to buy the security and in case of ‘sell’, it is the lowest price that he is willing to accept.

Stop-Loss: This facility allows the user to release an order into the system, after the market price of the security reaches or crosses a threshold price called trigger price. For example, if for stop loss buy order, the trigger is $93.00, the limit price is $95.00 and the market (last traded) price is $90.00, then this order is released into the system once the  market price reaches or exceeds $93.00. This order is added to the regular lot book with time of triggering as the time stamp, as a limit order of $95.00. All stop loss orders are kept in a separate book (stop loss book) in the system until they are triggered.

Trigger Price: Price at which an order gets triggered from the stop loss book.

Limit Price: Price of the orders after triggering from stop loss book.

Other Conditional Orders

One cancels the other(OCO) - If one part(Buy/Sell) of the order is executed, then the other part is automatically canceled.

Entry Orders- If one part of the order is executed, the other part is to be placed into the system.

Entry loop- Looping of Entry orders indefinitely until user cancelled

Several combinations of the above orders are allowed providing flexibility to the buyer and sellers in the market.

Still orders can classified into many other types based upon the usage, Above classification is only the basic (main) classification.

SYNCHRONIZATION POINT

SYNCHRONIZATION POINT:

Synchronization is a step added to a test that instructs QTP to wait for the state of a property on a particular object to change before proceeding to the next step in the test.

Following are the options to Synchronize your test

        Click on Record>>Insert>> Synchronization point>>select the object and set the property

Window("Flight Reservation").WinRadioButton("First").Set

Window("Flight Reservation").WinButton("Insert Order").WaitProperty "enabled", True, 10000

Window("Flight Reservation").WinButton("Insert Order").Click

       Insert Exist: This statement instruct QTP to wait for the specified time until an object exist before continuing the test

Window("Flight Reservation").WinRadioButton("First").Set

If  Window("Flight Reservation").WinButton("Insert Order").Exist(10) Then

Window("Flight Reservation").WinButton("Insert Order").Click

End If

        Insert wait statement: This statement force QTP to wait for the specified time before continuing the test

Window("Flight Reservation").WinRadioButton("First").Set

wait(20)

Window("Flight Reservation").WinButton("Insert Order").Click

       Insert sync statement: This statement instruct QTP to wait until next page is completely loaded.

Browser("Browser").Page("Sign in to Yahoo! India").WebEdit("login").Set "seenumech"

Browser("Browser").Page("Sign in to Yahoo! India").WebEdit("passwd").SetSecure "4ee4b6107d983246bdc6b7b498bc7f153aa61b3a37f4f099f13080d13c96e0fe"

Browser("Browser").Page("Sign in to Yahoo! India").WebButton("Sign In").Click

Browser("Browser").Page("Sign in to Yahoo! India").Sync

Browser("Browser").Page("(24 unread) - seenumech").Link("Inbox 24").Click

      Modify time that quicktest wait for a webpage to load: This statement instruct QTP to wait for a web  page to load till time we mentioned

File>>Setting >>web tab

     Modify default timeout setting of test: Maximum time QTP wait for the object to appear

File>>Setting >>Run tab

File Types in QTP (File Extensions):

File Types in QTP (File Extensions):

QTP File	File Type
QTP Script File	.mts
Batch test File	.mtb
Environmental Variable Files	.txt, .ini, .xml
Input/output Data (Datatable)	.xls
Recovery Scenario Files	.qrs
Library Files	.vbs, .qfl, .txt
Object repository (Shared)	.tsr
Object repository (Per Action/Local)	.mtr
Action File	.mst
Virtual Object Collection	.vot

Best Stocks to invest in 2011

Below are some of the best stocks one can invest in 2011.

• Gandhimathi Appliances
• SBI
• Panama Petrochem
• Astral Poly Technik
• Photoquip
• Cravatex
• Page Industries
• Wim Plast