With a robotic frame. NET self-initiated test

Clayton Neal has more than 13 years of experience in software testing and quality assurance, including eight years of experience in the testing of Windows, Web, and mobile applications . He has worked at all levels in the test field. He recently worked as QA Manager in Bloomberg and Misys. At the same time he was Sogeti's self-motivated test consultant. Clayton on his own initiative to test the super infatuation, but also see how to personally successfully implement test self-initiative.

?

Test the advantages of self-initiative we are very clear, faster feedback problems, reduce manual testing, continuous integration is the one that is freely available. The more Test team members, the more the company uses its own initiative, the better. To do this, we have to think about the technical aspects of testing ourselves, and consider writing and implementing our own proactive testing of the non-technical staff level. Whether the development team is doing agile acceptance test drive development (ATDD), agile behavior-driven development (BDD) or using traditional waterfall methods, the more members the team can use to make their own initiative, the wider the scope of their own proactive testing coverage. The
Keyword Drive test is a way for you to proactively develop the reusable behavior within your application by using your own proactive project engineer. Non-technical users are then able to sort through the reusable keyword behavior Library, regardless of the input parameters, to determine the test example. For example, a keyword can either click the button (tap on a button control) or enter text (enter text in a text box control), and then these keyword can be used to fill in a login form and click OKButton. The advantage of this approach is that self-motivated project master concentrates on what they are good at: developing keyword's own proactive script or programming, using these keyword by non-technical testing staff and enterprise users, and writing test examples based on their domain and product knowledge, Finally make yourself active more effective.
? Robot Framework is a general keyword-based testing self-motivated framework that does not depend on any particular self-motivated tool (e.g. QTP, Ranorex, testcomplete, selenium, etc.), Instead, let yourself take the initiative to insert a keyword with this kind of self-motivated tool. The robot has installed a lot of keyword and has a very mature feature set, including: keyword condition run  ,
Test sample and test set [Setup] and [teardown] 
? data-driven keyword file, folder and process management for loop  
? HTML test report  
? Jenkins CI integration transforms the variable into a keyword and returns   from the keyword callout of the test example keyword;
? The last feature listed can be used to create keyword on an existing keyword. Make sure 1 see the growth of the "keyword Pyramid".

The bottom of the pyramid is the technical keyword that is developed by your own initiative Project master: The top is the function of the individual function behavior within the APPLICATION keyword: Finally, we summarize the business process keyword based on the function keyword to build the business process within the application. This kind of layering can be seen in table 1, for example.

Table 1. Keyword layering

Here, the Technical keyword is based on the implementation of its own initiative with the display control, function keyword in the application to perform a single function step; higher-level business processes test the end-to-end process within the application.
The robot framework can be used to load new keyword from python and Java libraries; NET keyword, you should take advantage of the remote service interface. The interface is the Xmlrpc interface, where the robot framework sends a request to a remote service to run a keyword. Of course, such remote services can be developed in whatever language supports XMLRPC. In particular, a remote service can be used. NET development allows the robot framework to run keyword. NET-based keyword in assembly. This method is seen in 2.

Figure 2. Remote Service structure diagram

n Robot remote (see http://code.google.com/p/nrobotremote/) is a capable to build. Netkeyword Library and the. NET Robot Framework remote server that is exposed to the robot framework through the XMLRPC protocol. The combination of the N Robot remote robot framework allows the initial self-initiated work to plan which tests need to be self-motivated and what keyword to develop, rather than designing a self-motivated framework before initiating a test plan that can be started. Remote development for n robots. Netkeyword is just a class that develops a public method. Each method is regarded as a keyword--such as:

The keyword class exposes two Keyword:clickbutton and Entertext. By creating the keyword class in the N robot remote and pointing the robot frame to the XMLRPC address, these can be implemented using the chosen self-motivated test tool and can be called through the robot framework. 3 of what you see.

Figure 3: A trial example using the robot frame of the N robot remote

In the example above, set a column to tell the robot frame that there is a remote keyword service on the http://localhost:8271 (note: In addition to the local host, it may be on a machine), And the keyword from the remote server will have the prefix N robot remote (whatever prefix is possible). Test example a column defines a test example called an administrator login, calling Keywordentertext to enter username and Password,keywordclickbutton to click OK. Such a test could have been written by a non-technical tester or business user in the early stages of development. The keyword library itself can be seen as a thin layer above the domain model of the application being measured. For example, assuming that the Selenium Page object is used, the keyword layer will be able to invoke the Page object and method sequentially, as seen in 4.

Figure 4. Keyword and domain layers

Such abstractions provide flexibility when the application changes, and often, when applications change, only domain models and keyword implementations change. Test example implementation does not have to be constant, because it is built at a higher level. Use the robot frame and. Netkeyword also enables different self-active tools to integrate with each other, allowing them to proactively choose the best self-motivated tool for the desired keyword behavior. For example, assuming that in a larger company, several self-motivated teams have been chosen to use different self-starter tools for different product modules, each team will be able to develop a domain model for its modules in their respective development language, such as a robotic framework capable of loading python, Java and (via N robot remote). Netkeyword. Test-case writers also have the same ability to use keyword from all of their own active teams in their test examples.

　　Summarize
By agreeing with non-technical users to write test examples at each stage of development, they transform their proactive behavior from abstraction to a reusable keyword that can be passed on to non-technical testing and business users to reduce their own proactive project master bottlenecks. The robotic framework, as a well-established General keyword framework, agrees to focus on its own initiative and the required keyword, rather than designing and implementing a testing framework. Using the robotic framework and the N robot to remotely extend keyword's own initiative to. NET, agrees that keyword leverages the advantages of the. NET Framework and its own proactive tools in. NET, and agrees to combine keyword from python and Java with the same test example.

Copyright notice: This article from SPASVO Software Testing network: http://www.spasvo.com/news/html/2014101194841.html

Original works, reproduced when you must be in the form of hyperlinks to the original source, author information and this statement, or will be held liable.

With a robotic frame. NET self-initiated test