for SBY

In my opinion, all of test automation framework supply nearly the same function, the only difference is make a friendlier user interface. We master the principle of the tools and learn the methods form the tool author. For the web application automation, below code show the nature. This is part of training to my co-worker.

[TestMethod]
        //Data-driven testing:read input/output data into test case form DB/excel/xml/csv
        //[DataSource("Driver={Microsoft Excel};Path={};DataAccessMethod.Sequential")]
        public void TC_IEDemo()
        { 
            //using mshtml;using SHDocVw;
            InternetExplorer ie = new InternetExplorer();
            ie.Visible = true;
            string url = "http://www.google.com";

            /*below code should be packaged to a helper class method: 
             * LaunchApp(Enum BrowserType), ie7-10;ff/Chrome/iOS 
            Process.Start("iexplore.exe", url);*/
            object nil = new object();
            ie.Navigate(url, ref nil, ref nil, ref nil, ref nil);
            Thread.Sleep(3000);//WaitForReady(int timeout)

            /* below code show the three key steps of an automation framework:
             Tips:
             1) make code strong: WaitForReady(int timeout); try/catch/finally
             2) application UI tree should serialize into XML and store into congif file
             3) package basic operation, such as each page need login
             4) User only need call high level methods: click-IEclick/FFclick/…
             5) Deal with the accident: win auto update */
            
            //1.Get the UI element tree and point to target element.
            HTMLDocument doc = ie.Document as HTMLDocument;
            HTMLInputElement tb_Serach = (HTMLInputElement)doc.getElementById("q");//byname,bygroupid
            tb_Serach.value = "evernote";
            HTMLInputElement btn_Search = (HTMLInputElement)doc.getElementById("btnSearch");
            
            //2.Simulate the user input: mouse, keyboard, touch, thinking time.
            btn_Search.click();//WaitForReady(int timeout)

            //3.Check the attribute of target element: name, value, status.
            HTMLInputElement btn_Status = (HTMLInputElement)doc.getElementById("btnStatus");
            Assert.AreEqual("res.enu.wintitle", btn_Status.title);//use resource file for Multiple languages
        }

Windows desktop development technical evolution history: win32 SDK; Win Form; WPF/Silverlight,

Test automation technical also changed with it, below show my experience.

Mind map is on the way…

Main technical	Details Methods	Comments(Disadvantage)
Win32API HWND Win Message Win Hook	FindWindowEx SendKey GetWindowText	Windows Spy++ is the famous   tool which use these   Win Hook is more powerful but   may course AUT crash or miss the bug   Tester need nearly the same technical   as Dev
MSAA	IAccessible:: accName Get_accChild/Parent…	AccExplorer   Need Dev implement the   IAccessible interface
UIAutomation	UIA Property: Name/ID… UIA Pattern: Select/Expand… UIA Event: OnComplete…	First real framework for test   automation, Win32API is for Dev and MSAA is for special people to use windows   application.   UISpy