Selenium quick start note

本文详细介绍了Selenium自动化测试工具的各个组件,包括Selenium IDE、Selenium RC、Selenium WebDriver和Selenium Grid的功能和使用场景。同时,文章提供了Selenium支持的浏览器和操作系统列表,以及如何使用Selenium WebDriver进行自动化测试的Java示例代码。

Selenium

Selenium automates browsers.

Selenium Introduction:

Selenium Types:

·         Selenium IDE: a Firefox add-on that will do simple record-and-playback of interactions with the browser

·         Selenium RC (Remote Control): Selenium 1. deprecated. WebDriver is the successor.

·         Selenium WebDriver: Selenium 2. a collection of language specific bindings to drive a browser -- the way it is meant to be driven.

·         Selenium Server: used by both WebDriver and Remote Control. Built-in grid capabilities.

·         Selenium-Grid: Selenium Grid allows you to run your tests in parallel, that is, different tests can be run at the same time on different remote machines.

Selenium-WebDriver supports the following browsers along with the operating systems these browsers are compatible with.

·         Google Chrome 12.0.712.0+

·         Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable

·         Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7

·         Opera 11.5+

·         HtmlUnit 2.9

·         Android – 2.3+ for phones and tablets (devices & emulators)

·         iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

  

Selenium IDE note:

                Use guide: http://seleniumhq.org/docs/02_selenium_ide.html

                                Install, launch IDE;

                IDE feature:

                                add test case/suite, record, edit, run, log, reference;

                                export html/junit/python/c#/TestNG/Ruby;

                Export script types:

WebDriver

Remote Control

WebDriver Backend (java only)

 

Selenese – Selenium commands:

Command reference:http://release.seleniumhq.org/selenium-core/1.0.1/reference.html

                Actions: do things like “click this link”, some with “AndWait” suffix.

                Accessors: examine the status and store the results in variables;

                Assertions: verify that the state conforms to what’s expected. All in 3 modes:

assert” (once it fails, test is aborted),

verify” (once it fails, test will continue)

waitFor” (test halts after timeout).

 

Selenium 2.0 and WebDriver     http://seleniumhq.org/docs/03_webdriver.html

                Some reason why you will need the Selenium-Server -

·         You are using Selenium-Grid to distribute your tests over many machines / VMs.

·         You want to connect to a remote machine that has a particular browser version that is not on your current machine.

·         You are not using the Java bindings and would like to use HtmlUnit Driver

 

Java env setup with Maven:

                Maven 3.0.3: http://maven.apache.org/download.html

                selenium-java  for Maven: http://seleniumhq.org/download/maven.html

1.       Download Maven and add it to path;

2.       Create a pom.xml in your project and run “mvn clean install” in your project folder; (This will download Selenium and all its dependencies and will add them to the project.)

3.       Import your project into Eclipse after you run “mvn eclipse:eclipse” to generate project files for Eclipse. Your Eclipse must have m2eclipse installed (http://m2eclipse.sonatype.org/installing-m2eclipse.html for Eclipse 3.5.2 and 3.6.1 only).

pom.xml: 

 <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <groupId>MySel20Proj</groupId>
        <artifactId>MySel20Proj</artifactId>
        <version>1.0</version>
        <dependencies>
            <dependency>
                <groupId>org.seleniumhq.selenium</groupId>
                <artifactId>selenium-java</artifactId>
                <version>2.12.0</version>
            </dependency>
        </dependencies>
</project>

 Java test sample:

 

package org.openqa.selenium.example;

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.support.ui.ExpectedCondition;
import org.openqa.selenium.support.ui.WebDriverWait;

public class Selenium2Example  {
    public static void main(String[] args) {
        // Create a new instance of the Firefox driver
        // Notice that the remainder of the code relies on the interface,
        // not the implementation.
        WebDriver driver = new FirefoxDriver();

        // And now use this to visit Google
        driver.get("http://www.google.com/");
        // Alternatively the same thing can be done like this
        // driver.navigate().to("http://www.google.com/");

        // Find the text input element by its name
        WebElement element = driver.findElement(By.name("q"));

        // Enter something to search for
        element.sendKeys("Cheese!");

        // Now submit the form. WebDriver will find the form for us from the element
        element.submit();

        // Check the title of the page
        System.out.println("Page title is: " + driver.getTitle());
       
        // Google's search is rendered dynamically with JavaScript.
        // Wait for the page to load, timeout after 10 seconds
        (new WebDriverWait(driver, 10)).until(new ExpectedCondition<Boolean>() {
            public Boolean apply(WebDriver d) {
                return d.getTitle().toLowerCase().startsWith("cheese!");
            }
        });

        // Should see: "cheese! - Google Search"
        System.out.println("Page title is: " + driver.getTitle());
       
        //Close the browser
        driver.quit();
    }
}

 

Here is a guide on Jave env setup without Maven: http://www.silverwareconsulting.com/index.cfm/2010/5/17/Getting-Started-with-WebDriver-a-Browser-Automation-Tool

 

References:

http://seleniumhq.org/

Blog: http://seleniumhq.wordpress.com/

 

docs

http://www.ibm.com/developerworks/cn/java/wa-selenium-ajax/

http://www.ibm.com/developerworks/cn/opensource/os-webautoselenium/

http://www.cnblogs.com/hyddd/archive/2009/05/30/1492536.html

 

转载于:https://www.cnblogs.com/markjiao/archive/2011/11/17/2252834.html

# snmp_exporter ## Getting started To make it easy for you to get started with GitLab, here's a list of recommended next steps. Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! ## Add your files - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: ``` cd existing_repo git remote add origin https://10.6.80.1/ops/snmp_exporter.git git branch -M main git push -uf origin main ``` ## Integrate with your tools - [ ] [Set up project integrations](https://10.6.80.1/ops/snmp_exporter/-/settings/integrations) ## Collaborate with your team - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) - [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) ## Test and Deploy Use the built-in continuous integration in GitLab. - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) *** # Editing this README When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. ## Suggestions for a good README Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. ## Name Choose a self-explaining name for your project. ## Description Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. ## Badges On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. ## Visuals Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. ## Installation Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. ## Usage Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. ## Support Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. ## Roadmap If you have ideas for releases in the future, it is a good idea to list them in the README. ## Contributing State if you are open to contributions and what your requirements are for accepting them. For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. ## Authors and acknowledgment Show your appreciation to those who have contributed to the project. ## License For open source projects, say how it is licensed. ## Project status If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. 翻译以上内容 并总结使用方法
09-04
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值