CSC/ECE 517 Spring 2016/Write automated tests for WebDriver - Revision history

Ndhanir at 05:54, 4 May 2016

2016-05-04T05:54:03Z

← Older revision		Revision as of 05:54, 4 May 2016
Line 3:		Line 3:
	== Write automated tests for the WebDriver server ==		== Write automated tests for the WebDriver server ==

	~~ServoServo~~ is an open source prototype web browser layout engine being developed by Mozilla, and it is written in Rust language. It is currently developed on 64bit OS X, 64bit Linux, Android, and Gonk (Firefox OS). The main idea is to create a highly parallel environment, in which different components can be handled by fine grained, isolated tasks. The different components can be rendering, HTML parsing, etc.		Servo is an open source prototype web browser layout engine being developed by Mozilla, and it is written in Rust language. It is currently developed on 64bit OS X, 64bit Linux, Android, and Gonk (Firefox OS). The main idea is to create a highly parallel environment, in which different components can be handled by fine grained, isolated tasks. The different components can be rendering, HTML parsing, etc.

	== Background information: ==		== Background information: ==
Line 46:		Line 46:
	1. Execute tests on a standalone HTTP server: In this we wanted to test the functionality if a web page opens as expected on the wed driver engine. We have implemented this by giving a URL which opens a web page whose actual URL is different when the page opens. We matched the web page expected with the one that is opened to successfully execute the test case.		1. Execute tests on a standalone HTTP server: In this we wanted to test the functionality if a web page opens as expected on the wed driver engine. We have implemented this by giving a URL which opens a web page whose actual URL is different when the page opens. We matched the web page expected with the one that is opened to successfully execute the test case.

	2.

	== Implementation ==		== Implementation ==

Skunapa: /* Design pattern */

2016-04-28T04:01:34Z

Design pattern

← Older revision		Revision as of 04:01, 28 April 2016
Line 39:		Line 39:
	* Loading a page that loads slower than the timeout, and ensure we get the correct error message		* Loading a page that loads slower than the timeout, and ensure we get the correct error message

	== Design ~~pattern~~ ==		== Design ==
	Design patterns are not applicable as our task involved writing automated tests in python. However, the Implementation section below provides details of the steps the way it was implemented.		Design patterns are not applicable as our task involved writing automated tests in python. However, the Implementation section below provides details of the steps the way it was implemented.

			We have implemented the test cases based on the input from the Mozilla team and there were several major tasks that were implemented.

			1. Execute tests on a standalone HTTP server: In this we wanted to test the functionality if a web page opens as expected on the wed driver engine. We have implemented this by giving a URL which opens a web page whose actual URL is different when the page opens. We matched the web page expected with the one that is opened to successfully execute the test case.

			2.

	== Implementation ==		== Implementation ==

Skunapa: /* Servo: */

2016-04-28T00:58:43Z

Servo:

← Older revision		Revision as of 00:58, 28 April 2016
Line 11:		Line 11:

	=== Servo: ===		=== Servo: ===
			Servo is a project to develop a new Web browser engine to help mitigate vulnerabilities associated with incorrect memory management and data races. Servo is written in Rust, a new language designed specifically with Servo's requirements in mind. Rust provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.

			Servo is focused both on supporting a full Web browser, through the use of the purely HTML-based user interface Browser.html and on creating a solid, embeddable engine. Although Servo was originally a research project, it was implemented with the goal of having production-quality code and is in the process of shipping several of its components in the Firefox browser.

	[[File:ServoArchitecture.JPG]]		[[File:ServoArchitecture.JPG]]

			The above diagram denotes several of the tasks that are associated with building the Servo web browser. Each of the boxes represents a task that is implemented in Rust and the lines indicates relationships between the tasks.

	=== WebDriver: ===		=== WebDriver: ===

Skunapa: /* Servo: */

2016-04-28T00:54:17Z

Servo:

← Older revision		Revision as of 00:54, 28 April 2016
Line 11:		Line 11:

	=== Servo: ===		=== Servo: ===
	[[File:ServoArchitecture.~~PNG~~]]		[[File:ServoArchitecture.JPG]]

	=== WebDriver: ===		=== WebDriver: ===

Skunapa: /* Background information: */

2016-04-28T00:54:01Z

Background information:

← Older revision		Revision as of 00:54, 28 April 2016
Line 9:		Line 9:
	=== Python: ===		=== Python: ===
	Python is a widely used high-level, general-purpose, interpreted, dynamic programming language. Python supports multiple programming paradigms, including object oriented, imperative and functional programming or procedural styles. It features a dynamic type system and automatic memory management and has a large and comprehensive standard library. Modules for creating graphical user interfaces, connecting to relational databases, pseudorandom number generators, arithmetic with arbitrary precision decimals,[77] manipulating regular expressions, and doing unit testing are also included.		Python is a widely used high-level, general-purpose, interpreted, dynamic programming language. Python supports multiple programming paradigms, including object oriented, imperative and functional programming or procedural styles. It features a dynamic type system and automatic memory management and has a large and comprehensive standard library. Modules for creating graphical user interfaces, connecting to relational databases, pseudorandom number generators, arithmetic with arbitrary precision decimals,[77] manipulating regular expressions, and doing unit testing are also included.

			=== Servo: ===
			[[File:ServoArchitecture.PNG]]

	=== WebDriver: ===		=== WebDriver: ===

Kgala: /* Implementation */

2016-04-05T00:21:19Z

Implementation

← Older revision		Revision as of 00:21, 5 April 2016
Line 34:		Line 34:

	== Implementation ==		== Implementation ==
			===Initial Steps===
	The following steps were followed to meet the project requirements as per this github page.		The following steps were followed to meet the project requirements as per this github page.

Line 42:		Line 43:

	We created tests in test.py and test1.py for loading a particular URL, asserting that the resulting page is the expected url.		We created tests in test.py and test1.py for loading a particular URL, asserting that the resulting page is the expected url.


			===Subsequent Steps===
			===Step 1:===
			We would create 3 different test.py files for each of the different tests that would reside in tests/webdriver folder.

			===Step 2:===
			Creating a ServoProcess that would be used by the test.py files to start a servo session.

			===Step 3:===
			Catching exceptions when the tests fail and displaying them in proper format based on the kind of different error.

	== Testing ==		== Testing ==

Kgala at 00:15, 5 April 2016

2016-04-05T00:15:58Z

← Older revision		Revision as of 00:15, 5 April 2016
Line 14:		Line 14:

	== Scope ==		== Scope ==
			===Initial Steps===
	* Compile Servo and ensure that it runs on <code>tests/html/about-mozilla.html</code>		* Compile Servo and ensure that it runs on <code>tests/html/about-mozilla.html</code>
	* To run a simple webdriver script using the python client against Servo.		* To run a simple webdriver script using the python client against Servo.
	* Create a<code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> that will import each python file in the directory and execute the <code>test</code> method contained within it by invoking the Servo process before running each test, and killing it after each test finishes.		* Create a<code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> that will import each python file in the directory and execute the <code>test</code> method contained within it by invoking the Servo process before running each test, and killing it after each test finishes.
	* Create a <code>webdriver</code> directory under <code>tests</code> where the forthcoming tests will reside.		* Create a <code>webdriver</code> directory under <code>tests</code> where the forthcoming tests will reside.
	* ~~Write~~ an automated test for loading a particular URL, asserting that the resulting page is the expected url.		* Writing an automated test for loading a particular URL, asserting that the resulting page is the expected url.
			===Subsequent Steps===
			* Writing tests that exercise the lower-level command API (eg. self.send_command("POST", "url", body)) to test server capabilities:
			* Writing a test with a simple get to a url that exists on the server, ensure that we get the right response type
			* Sending a non-string as the URL and ensuring that we get the right kind of error message.
			* Trying other kinds of non-conforming messages e.g. ones with extra fields (should be ignored) or no url field (should return the correct type of error)
			* Testing that we are actually loading the correct page. This will require the use of some other webdriver functions e.g. to get an element's text, or take a screenshot
			* Testing that Get always navigates the top level browsing context (by navigating to a page with an iframe, setting the current bc to that iframe, and ensuring that it is not just the iframe that is navigated).
			* Trying Get with pages that return non-200 responses.
			* Loading a page that loads slower than the timeout, and ensure we get the correct error message

	== Design pattern ==		== Design pattern ==

Kgala at 00:36, 24 March 2016

2016-03-24T00:36:42Z

← Older revision		Revision as of 00:36, 24 March 2016
Line 28:		Line 28:
	=== Step 1: ===		=== Step 1: ===
	We created a new <code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> file. It imports each python file in the directory and executes the <code>test</code> method contained within it.		We created a new <code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> file. It imports each python file in the directory and executes the <code>test</code> method contained within it.

	~~[[File:webdriver_test.jpg]]~~

	=== Step 2: ===		=== Step 2: ===

Kgala at 00:35, 24 March 2016

2016-03-24T00:35:07Z

← Older revision		Revision as of 00:35, 24 March 2016
Line 28:		Line 28:
	=== Step 1: ===		=== Step 1: ===
	We created a new <code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> file. It imports each python file in the directory and executes the <code>test</code> method contained within it.		We created a new <code>mach</code> command (<code>test-webdriver</code>) in <code>python/servo/testing_commands.py</code> file. It imports each python file in the directory and executes the <code>test</code> method contained within it.

			[[File:webdriver_test.jpg]]

	=== Step 2: ===		=== Step 2: ===

Anayakv: moved User:Anayakv to CSC/ECE 517 Spring 2016/Write automated tests for WebDriver

2016-03-24T00:33:10Z

moved User:Anayakv to CSC/ECE 517 Spring 2016/Write automated tests for WebDriver

← Older revision	Revision as of 00:33, 24 March 2016
(No difference)