Pros and cons of end to end testing tools

本贴最后更新于 1839 天前,其中的信息可能已经时移世改

My background in test automation is based on using Selenium WebDriver and Java. Since JavaScript has been widely used for testing web applications, I have decided to investigate tools currently available on the market. I will use these tools to make different scripts and hence find their advantages and disadvantages.

I have investigated the following tools and syntax for automation:

  1. Selenium Webdriver + Java
  2. Selenium WebDriver + Cucumber + Java
  3. Selenium WebDriver + Jasmine syntax for JavaScript applications
  4. Selenium WebDriver + Mocha syntax for JavaScript applications
  5. Cypress
  6. Selenium WebDriver + Protractor
  7. Selenium WebDriver + NightWatch
  8. Selenium WebDriver + WebDriverIO

The focus of this article is not on finding advantages or disadvantages of Selenium WebDriver, but I mainly focus on investigating the pros and the cons of different tools/frameworks in combination with Selenium WebDriver. Thus this article may be useful for those who already know Selenium and would like to gain knowledge of using different tools in combination with Selenium.

I have created a simple test and will try to implement its script by using all the above automation tools. I have chosen Amazon website as most of its elements are identified by an id and this makes it easy to find an element.

1. Let us start from the first one in the above list, which is** “Selenium WebDriver + Java”.** For many years this has been a popular style for making automation and I personally have been using it. In the following you see a test that is implemented in this style.


// open a browser
driver.get("https://www.amazon.com/");

// click on Your Amazon.com link
WebElement yourAmazon = driver.findElement(By.id("nav-your-amazon"));
yourAmazon.click();

// enter your email address
WebElement email = driver.findElement(By.id("ap_email"));
email.sendKeys("Test123@email.com");

// enter your password address
WebElement password = driver.findElement(By.id("ap_password"));
password.sendKeys("1234");

//press sign in button
WebElement signIn =driver.findElement(By.id("signInSubmit"));
signIn.click();

// check if the error message is displayed
WebElement errorMessageBox = driver.findElement(By.id("auth-error-message-box"));
errorMessageBox.isDisplayed();

//close browser
driver.close();

After making the above script, advantages of this style can be summarized as follows:

  • It has a quick and popular setup. For setting up this test, you only need to import Driver and the Selenium library Java. If you need more information on how to set up your test, please read here: https://www.guru99.com/intellij-selenium-webdriver.html
  • If any help in making scripts is needed, there are lots of sources available online that can be used by testers.
  • A very basic knowledge of Java is enough for implementing the scripts.
  • Java structure can be adjusted quite easily within a development team who know the Java. I highly recommend using this style if a tester is in a Java team, as it is productive for the team to create scripts. The team members can easily pick up automation tests to help the tester, thus tests are not only implemented by the tester but by the whole team.

Disadvantages of this style can be summarised as follows:

  • It is not possible to add a clear description for each step. If you are looking for a clean syntax, the combination of Java and Selenium doesn’t provide it for you. You can add a description of each step as a comment but this will not be displayed in the logs if the test fails.
  • You can also add a clear error message for each test to make it easier to find the failing step, however it is hard to keep this syntax clean.

=====================================================================================

  1. Selenium WebDriver + Cucumber + Java:

https://www.stevefenton.co.uk/2015/01/getting-started-with-bdd-intellij

The test includes three parts:

  • Feature file, which is a clear description for each step of your test using Gherkin syntax.
  • Step file, which is the script for matching the features and the Java code.
  • TestRun, which is the configuration setup for running your test.

Let’s see how the test is written down :

[1]: Feature file:


Feature: CucumberJava
        Scenario: Login functionality exists
        Given I have open amazon website
        And click on your Amazon.com link
        When  enter username "test@gmail.com" and password "123"
        When press sign in button
        Then the error message box is displayed

[2]: Step file:


   class cucumberJava {
   WebDriver driver = null;

   @Given("^I have open amazon website$")
   public void openBrowser() {
       driver = new FirefoxDriver();
       driver.navigate().to("https://www.amazon.com/");
   }

   @And("^click on your Amazon.com link$")
    public void clickOnYourAmazon(){
       driver.findElement(By.id("nav-your-amazon")).click();
   }

   @When("^enter username \"(.*)\" and password \"(.*)\" $")
      public void UserAndPassword(String username,String password){
        driver.findElement(By.id("ap_email")).sendKeys(username);
        driver.findElement(By.id("ap_password")).sendKeys(password);
   }

   @When("^press sign in button$")
     public void SignInButton(){
          driver.findElement(By.id("signInSubmit")).click();
   }

   @Then("^the error message box is displayed$")
   public void errorMessage() {
       if(driver.findElement(By.id("auth-error-message-boc")).isDisplayed()) {
           System.out.println("Test 1 Pass");
       } else {
           System.out.println("Test 1 Fail");
       }
       driver.close();
   }
}

3. TestRun:


package cucumberJava;

import org.junit.runner.RunWith;
import cucumber.junit.Cucumber;

@RunWith(Cucumber.class)
@Cucumber.Options(format = {"pretty", "html:target/cucumber"},
       glue = {"cucumberJava"},
       features = {"src/test/java/cucumberJava/cucumberJava.feature"}

)
public class runTest { }

Advantages:

  • A descriptive test step is helpful when a test fails. This is considered mainly as an advantage for business people but I believe this is also advantageous for the development team as it gives them a clean and readable description of test steps (for example why this test, how it is done, etc.), and maintenance of automation tests in large projects will be easier due to the descriptive steps.
  • It is a comfortable tool for development teams who build java applications with java language, It will help the team to be more productive.

Disadvantages:

  • Your feature file can easily become a very large and messy file.
  • Running tests can take quite some time, especially when you want to run your test in different browsers.
  • If you are going to test a JavaScript application by Cucumber and Java, it might be difficult for the development team to adjust itself which is less productive.
  • It was not quick or easy to set up, it took me some time to figure out how to link the features file with the steps file!!
  • Most people use the BDD given, when, then syntax in a structure which is not sensible. It is essential to know that this syntax is designed for the following reasons:
    1. Given provides context for the test scenario that is going to be executed, such as the point in your application that the test occurs as well as any prerequisite data.
    2. When specifies the set of actions that triggers the test, such as user or subsystem actions.
    3. Then specifies the expected result of the test.

=====================================================================================

Let us now look at the following tools which are mostly used for JavaScript applications.

3. Selenium WebDriver with Jasmine Synatx:

I started to set up my test based on the information in the blog post: http://blog.scottlogic.com/2017/08/24/adding-webdriver-tests-to-create-react-app-generated-projects.html

The setup is quick and easy, but it has three different parts:

  • Page objects: the place where you find your elements by css/xpath.
  • Specs: for writing the actual script.
  • Configuration files: you can set up your “tear down” over here.

Let us again create our script for checking the correct error message on Amazon and see what the syntax looks like with this structure:

Page object:


const yourAmazonSelector = { css: '#nav-your-amazon' };
const emailSelector = { css: '#ap_email' };
const passwordSelector = { css: '#ap_password' };
const signInSelector = { css: '#signInSubmit' };
const errorMessageSelector = { css: '#auth-error-message-box' };

export const yourAmazon = () => body().findElement(yourAmazonSelector);

export const email = () => body().findElement(emailSelector);

export const password = () => body().findElement(passwordSelector);

export const continueSignIn = () => body().findElement(continueButton);

export const signIn = () => body().findElement(signInSelector);

export const errorMessage = () => body().findElement(errorMessageSelector);

Specs:


import { yourAmazon, email, password, errorMessage, signIn, continueSignIn } from '../pageObjects/app';
import { load } from '../pageObjects/index';

describe('app', async () => {
 beforeAll(async () => {
   await load();

 });

 let randomEmail = Math.random();
 let randomPassword = Math.random();

 it('should display the correct error message for incorrect login details', async () => {
   await yourAmazon().click();
   await email().sendKeys(randomEmail + "@gmail.com");
   await password().sendKeys(randomPassword);
   await signIn().click();
   expect(await errorMessage().isDisplayed()).toBe(true);

 });

});

Advantages:

  • There are no other tools involved in this test, it is only Selenium WebDriver + Jasmine syntax.
  • In Jasmine we need to use the describe function that helps for grouping our tests together.
  • Jasmine comes with a number of matchers that help you make a variety of assertions. You should read the Jasmine documentation to see what they are. To use Jasmine with Karma, some people use the karma-jasmine test runner.
  • It has Angular support.
  • Jasmine's beforeAll() hook is often useful for sharing test setup - either to reduce test run-time or simply to make for more focused test cases and it reduces lines of code too!!

Disadvantages:

  • There is less documentation available for finding information about setting up your css in the case of having multiple ids for one element.
  • It took me a while to figure out how to use “beforeAll()” instead of “beforeEach()” in my specs: if you use “beforeEach” then you can not use nested test steps, because in each step it tries to open a new browser and running a new test and it runs before each 'it' block!! However if you use “beforeAll”, you can have multiple nested steps in the same test.

====================================================================================

4. Selenium WebDriver with Mocha syntax:

Let’s start to make a test with Selenium and Mocha syntax by following this document: http://testerstories.com/2016/02/javascript-with-selenium-webdriver-and-mocha/

The setup was quick and easy. Mocha is a simple, flexible and fun, java-script test framework for node.js and browsers.

Here's the script using Mocha:


 var assert = require('assert'),
   fs = require('fs'),
   test = require('selenium-webdriver/testing'),
   webdriver = require('selenium-webdriver');

test.describe('My Website', function () {
   this.timeout(15000);
   var driver;
   test.before(function () {
       driver = new webdriver.Builder().withCapabilities(webdriver.Capabilities.chrome()).build();
   });

   var emailRandom = Math.random();
   var passwordRandom = Math.random();

   test.it('should display the correct error message with incorrect login information', function () {
       driver.get('https://www.amazon.com/');
       driver.findElement(webdriver.By.id('nav-your-amazon')).click();
       driver.findElement(webdriver.By.id('ap_email')).sendKeys(emailRandom + "@gmail.com");
       driver.findElement(webdriver.By.id('ap_password')).sendKeys(passwordRandom);
       driver.findElement(webdriver.By.id('signInSubmit')).click();
       var errorMessage = driver.findElement(webdriver.By.id('auth-error-message-box')).isDisplayed();
       if (errorMessage == true){
           return true;
       }else return false;
   });
   test.after(function () {
       driver.quit();
   });
});

Advantages:

  • Mocha's before() hook is often useful for sharing test setup - either to reduce test run-time or simply to make for more focused test cases.
  • There are no other tools involved in this test, it is only Selenium WebDriver + Mocha syntax.
  • In Mocha we need to use the describe function that helps for grouping our tests together.

=========================================================================

5. Cypress :

While I was busy with writing this blog post for different tools that use Selenium for end to end testing, cypress got my attention and I started to make a simple script by using Cypress. Cypress doesn’t use Selenium and it is a bit different with the above tools that I have experimented.

The setup was quick and fast, you don't need any special configuration for running your test.

If you are new in using Cypress, you can follow the following website for installing it: https://docs.cypress.io/guides/getting-started/installing-cypress.html#

If you need more sources for getting familiar with cypress, you can use the following: https://example.cypress.io/

I have created my running script for Amazon website here:


describe('should display a correct error message when you enter wrong login information', function () {
 before(function () {
   cy.visit('https://www.amazon.com/')
 })

 var randomEmail = Math.random();
 var randomPassword = Math.random();

 it('displays a correct error message', function () {
   cy.get('#nav-your-amazon').click()
   cy.get('#ap_email').type(randomEmail + '@gmail.com')
   cy.get('#ap_password').type(randomPassword)
   cy.get('#signInSubmit').click()
   cy.get('#auth-error-message-box').should('be.visible')
 })
})

I like cypress a lot because of the following reasons:

  • Cypress does not use Selenium: most of the end to end tools that we have experimented with, are using Selenium, that’s why they have almost the same problems.
  • Cypress supports any framework or website quite well: There are hundreds of projects using the latest React, Angular, Vue, Elm, etc. frameworks. Cypress also works equally well on older server rendered pages or applications.
  • Cypress tests are only written in JavaScript: While you can compile down to JavaScript from any other language, ultimately the test code is executed inside the browser itself. There are no languages or driver bindings - there is and will only ever be just JavaScript.
  • There are no dependencies, you put your test in package.json and that’s it.
  • Cypress runs much, much faster in comparison with the end to end tools by Selenium that we have experimented.
  • There is screen shot for every step, of your script, which can be quite helpful if there is any false passing or failing test, yeah good for debugging!!
  • Cypress has a clear cyntax, it is easy to read it, you will like it!!

Disadvantages:

  • The structure was different to the other Selenium end to end tools, so at first you may need to spend more time understanding the structure and finding the best way to create your scripts.
  • Community: As Cypress is relatively new, the community is small. You will have trouble finding answers to problems etc.
  • Features. No file upload support. No cross-browsers testing. Who knows when these things will be covered, as for big projects these features are crucial.
  • Page Object Model. It is something that has already been proven by time. Cypress supports a different approach which could be controversial. More detail on this is here: Cypress POM
  • It's only available for only one client (language) i.e for JavaScript only. So to work with it you must know JavaScript: however this might be an advantage for JavaScript application, but I would like to put it as a disadvantages for those who have difficulties with javascript.

reference for more information

=============================================================================

6. Protractor tool with Selenium WebDriver :

I followed this tutorial for making my first script with protractor and Selenium WebDriver:https://github.com/angular/protractor/blob/master/docs/tutorial.md

And this is my running script for Amazon website:


 // spec.js
describe('should display a correct error message when I enter wrong login information', function () {
 it('correct error message', function () {
   browser.waitForAngularEnabled(false);
   browser.get('https://www.amazon.com/');

   //click on orders link
   const Orders = element(by.id('nav-orders'));
   Orders.click();
   // enter your email
   const email = element(by.id('ap_email'));
   email.sendKeys('test@gmail.com');
   // enter your password
   const password = element(by.id('ap_password'));
   password.sendKeys('7899');

   //check if the error box is not displayed
   const errorBox1 = element(by.id('auth-warning-message-box'));
   expect(errorBox1.isPresent()).toEqual(false);

   //click on sign in button
   const signIn = element(by.id('signInSubmit'));
   signIn.click();

   // check if the error box is displayed
   const errorBox = element(by.id('auth-error-message-box'));
   expect(errorBox.isDisplayed()).toEqual(true);

   const message = element(by.css('.a-list-item'));
   expect(message.getText()).toEqual('To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below.');

 });
});

Advantages:

  • Suitable for both Angular and non-Angular apps. Protractor gives extra advantages for testing Angular apps but your app should not necessarily use it, If you have an application that is not Angular and you would like to use Protractor, you always need to add the following to your spec BEFORE opening your browsers:

    browser.waitForAngularEnabled(false);
    
  • Protractor has built a support for identifying the elements for angular.js applications which is the following:


 by.binding 
 by.excatBinding 
 by.model 
 by.repeater 
 by.exactRepeater 
 by.options

If you would like to know more about the differences of these Locator Strategies, please read the following article: http://www.webdriverjs.com/angular-specific-locators-in-protractor/

  • Parallel testing through several browsers. It supports cross-browser testing. Even more ,  you can run several browsers instances simultaneously!

Disadvantages:

  • Debugging: I personally found it tricky to debug protractor.
  • It's available for only one client (language) i.e. for JavaScript only. So you must know JavaScript to work with it.
  • It does not support automating mobile Apps.
  • It is implemented as a wrapper to the WebdriverJs. So there is one more layer added in between Selenium server and the Protractor. If there is an issue with WebdriverJs, the Protractor team should wait for the WebDriverJs team to fix that issue.

===================================================================================

7. NightWatch with Selenium WebDriver:

I followed this tutorials for making my first script by NightWatch and Selenium WebDriver: https://github.com/dwyl/learn-nightwatch Below is my script for Amazon website. The test consists of three parts: * Package * Nightwatch configuration file * script The package consisted of the following:


  {
  "name": "nightwatch",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "nightwatch",
    "e2e-setup": "selenium-standalone install"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "babel-cli": "^6.26.0",
    "babel-plugin-add-module-exports": "^0.2.1",
    "babel-preset-es2015": "^6.24.1",
    "selenium-standalone": "^6.12.0"
  }
}

The configuration file for this script consists of the following:


  {
    "src_folders" : ["tests"],
    "output_folder" : "reports",

    "selenium" : {
      "start_process" : true,
      "server_path" : "bin\selenium-server-standalone-3.3.1.jar",
      "log_path" : "",
      "port" : 4445,
      "cli_args" : {
        "webdriver.chrome.driver" : "bin\chromedriver.exe"
      }
    },

    "test_settings" : {
      "default" : {
        "launch_url" : "http://localhost",
        "selenium_port"  : 4445,
        "selenium_host"  : "localhost",
        "desiredCapabilities": {
          "browserName": "chrome",
          "javascriptEnabled": true,
          "acceptSslCerts": true
        }
      }
    },

    "scripts": {
      "test-e2e": "nightwatch"
    }

  }

There is a bug in NightWatch using Selenium port 4444. The Selenium server didn’t run when I specified port 4444, but it run successfully by changing the port to 4445.

The script looks like this:


module.exports = {
    'Should display a correct error message when you enter a wrong login information' : function (client) {
            client
            .url ('http://www.amazon.com/')
            .waitForElementVisible('body', 1000)
            .click('#nav-orders')
        .setValue('#ap_email', 'test@gmail.com')
        .setValue('#ap_password' ,'123')
        .click('#signInSubmit')
        .assert.visible('#auth-error-message-box')
        .end();

    }
};

Advantages:

  • Clean syntax: Simple but powerful syntax enables you to write tests very quickly.
  • Built-in test runner: Built-in command-line test runner can run the tests either sequentially or in parallel, together, by group, tags, or single.
  • Cloud services support: Works with cloud testing providers, such as SauceLabs and BrowserStack.
  • CSS & Xpath support: Either CSS or Xpath selectors can be used to locate and verify elements on the page or execute commands.
  • Continuous Integration support: JUnit XML reporting is built-in so you can integrate your tests in your build process with systems such as Teamcity, Jenkins, Hudson etc.

Disadvantages:

  • It does not have many choices for unit test frameworks as it has an own testing framework and also support Mocha.
  • Slightly lesser support in compare with WebDriverIO and Protractor.

====================================================================

8. WebDriverIO with Selenium WebDriver: I followed this tutorial for making my first script by WebDriverIO and Selenium WebDriver:http://blog.kevinlamping.com/testing-your-login-an-in-depth-webdriverio-tutorial/

This test also consisted of three parts:

  • package
  • wdio.config
  • script

The package and the configuration file is quite similar to NightWatch test, so I only put the script here:


describe('Login Page', function () {
   it('Should display a correct error message with wrong login information', function () {
       browser.url('/');
       browser.click('#nav-your-amazon');
       browser.setValue('#ap_email', 'test@gmail.com');
       browser.setValue('#ap_password', '123');
       browser.click('#signInSubmit');
       browser.isVisible('#auth-error-message-box')
   })
})

Advantages:

  • It has support for most BDD and TDD test frameworks.
  • It has good support, enthusiastic developer community, and end users which give it an edge over NightwatchJS.
  • It can be used with ‘webdrivercss’ to compare css stylings of an element in the webpage.
  • Works with any testing framework or assertion library: WebdriverIO lets you use your favorite testing framework (Jasmine, Mocha, Cucumber) and assertion library (Chai for Mocha).

Disadvantages:

  • Since it is a custom implementation, it is also a disadvantage as it deviates from generic syntax which may confuse Selenium developers coming from other languages.
  • It can be used for automating AngularJS apps but it is not as customized as Protractor.
  • Must run with WDIO to debug: Tasks written in this beautiful Selenium API can only be debugged using the provided WDIO task runner. You can't set breakpoints within tasks, but you can have WDIO pause the run between Selenium commands.
  • I did not find much documents for latest version (4.0.5)

===============================================================================

Conclusion: In this document we considered a simple test and created its scripts by different end to end testing tools. We have experimented different syntaxes on those scripts. In my opinion the difference between these tools is not huge. The tool should be selected mainly based on your application and knowledge of the team. The latter is very important since automation is not the responsibility of individual team members, rather an entire team should contribute towards it. Learning a new programming or scripting language will definitely enhance the skills of team members but working on a common ground keep all team members motivated.

As a tester, you should find out the answers of the following questions by examining the application you are going to test:

  • Is the application built using Angular, React, etc.?
  • Are you looking for a special testing framework like Jasmine, Mocha, etc.?
  • Are you looking for a tool that supports mobile (APPIUM)?
  • Are you looking to test in any specific browser?

Depending on the answers of the above questions, you can select your suitable tool.

谢谢原作者,博客转自:https://blog.scottlogic.com/2018/01/08/pros-cons-e2e-testing-tools.html

  • App

    App(应用程序,Application 的缩写)一般指手机软件。

    90 引用 • 383 回帖
  • Java

    Java 是一种可以撰写跨平台应用软件的面向对象的程序设计语言,是由 Sun Microsystems 公司于 1995 年 5 月推出的。Java 技术具有卓越的通用性、高效性、平台移植性和安全性。

    3165 引用 • 8206 回帖
  • Python

    Python 是一种面向对象、直译式电脑编程语言,具有近二十年的发展历史,成熟且稳定。它包含了一组完善而且容易理解的标准库,能够轻松完成很多常见的任务。它的语法简捷和清晰,尽量使用无异义的英语单词,与其它大多数程序设计语言使用大括号不一样,它使用缩进来定义语句块。

    534 引用 • 671 回帖
  • Selenium
    16 引用 • 13 回帖

相关帖子

欢迎来到这里!

我们正在构建一个小众社区,大家在这里相互信任,以平等 • 自由 • 奔放的价值观进行分享交流。最终,希望大家能够找到与自己志同道合的伙伴,共同成长。

注册 关于
请输入回帖内容 ...

推荐标签 标签

  • ZeroNet

    ZeroNet 是一个基于比特币加密技术和 BT 网络技术的去中心化的、开放开源的网络和交流系统。

    1 引用 • 21 回帖 • 591 关注
  • Logseq

    Logseq 是一个隐私优先、开源的知识库工具。

    Logseq is a joyful, open-source outliner that works on top of local plain-text Markdown and Org-mode files. Use it to write, organize and share your thoughts, keep your to-do list, and build your own digital garden.

    4 引用 • 55 回帖 • 6 关注
  • 机器学习

    机器学习(Machine Learning)是一门多领域交叉学科,涉及概率论、统计学、逼近论、凸分析、算法复杂度理论等多门学科。专门研究计算机怎样模拟或实现人类的学习行为,以获取新的知识或技能,重新组织已有的知识结构使之不断改善自身的性能。

    76 引用 • 37 回帖
  • 国际化

    i18n(其来源是英文单词 internationalization 的首末字符 i 和 n,18 为中间的字符数)是“国际化”的简称。对程序来说,国际化是指在不修改代码的情况下,能根据不同语言及地区显示相应的界面。

    7 引用 • 26 回帖 • 1 关注
  • Q&A

    提问之前请先看《提问的智慧》,好的问题比好的答案更有价值。

    6364 引用 • 28618 回帖 • 264 关注
  • Kotlin

    Kotlin 是一种在 Java 虚拟机上运行的静态类型编程语言,由 JetBrains 设计开发并开源。Kotlin 可以编译成 Java 字节码,也可以编译成 JavaScript,方便在没有 JVM 的设备上运行。在 Google I/O 2017 中,Google 宣布 Kotlin 成为 Android 官方开发语言。

    19 引用 • 33 回帖 • 22 关注
  • uTools

    uTools 是一个极简、插件化、跨平台的现代桌面软件。通过自由选配丰富的插件,打造你得心应手的工具集合。

    5 引用 • 13 回帖
  • jsDelivr

    jsDelivr 是一个开源的 CDN 服务,可为 npm 包、GitHub 仓库提供免费、快速并且可靠的全球 CDN 加速服务。

    5 引用 • 31 回帖 • 33 关注
  • PHP

    PHP(Hypertext Preprocessor)是一种开源脚本语言。语法吸收了 C 语言、 Java 和 Perl 的特点,主要适用于 Web 开发领域,据说是世界上最好的编程语言。

    164 引用 • 407 回帖 • 523 关注
  • 程序员

    程序员是从事程序开发、程序维护的专业人员。

    529 引用 • 3527 回帖
  • 创造

    你创造的作品可能会帮助到很多人,如果是开源项目的话就更赞了!

    171 引用 • 988 回帖
  • abitmean

    有点意思就行了

    14 关注
  • IDEA

    IDEA 全称 IntelliJ IDEA,是一款 Java 语言开发的集成环境,在业界被公认为最好的 Java 开发工具之一。IDEA 是 JetBrains 公司的产品,这家公司总部位于捷克共和国的首都布拉格,开发人员以严谨著称的东欧程序员为主。

    180 引用 • 400 回帖
  • Bug

    Bug 本意是指臭虫、缺陷、损坏、犯贫、窃听器、小虫等。现在人们把在程序中一些缺陷或问题统称为 bug(漏洞)。

    76 引用 • 1738 回帖 • 2 关注
  • Sillot

    Sillot (汐洛)孵化自思源笔记,致力于服务智慧新彖乄,具有彖乄驱动、极致优雅、开发者友好的特点
    Github 地址:https://github.com/Hi-Windom/Sillot

    12 引用 • 26 关注
  • InfluxDB

    InfluxDB 是一个开源的没有外部依赖的时间序列数据库。适用于记录度量,事件及实时分析。

    2 引用 • 47 关注
  • Dubbo

    Dubbo 是一个分布式服务框架,致力于提供高性能和透明化的 RPC 远程服务调用方案,是 [阿里巴巴] SOA 服务化治理方案的核心框架,每天为 2,000+ 个服务提供 3,000,000,000+ 次访问量支持,并被广泛应用于阿里巴巴集团的各成员站点。

    60 引用 • 82 回帖 • 590 关注
  • 支付宝

    支付宝是全球领先的独立第三方支付平台,致力于为广大用户提供安全快速的电子支付/网上支付/安全支付/手机支付体验,及转账收款/水电煤缴费/信用卡还款/AA 收款等生活服务应用。

    29 引用 • 347 回帖 • 2 关注
  • 分享

    有什么新发现就分享给大家吧!

    240 引用 • 1729 回帖
  • 房星科技

    房星网,我们不和没有钱的程序员谈理想,我们要让程序员又有理想又有钱。我们有雄厚的房地产行业线下资源,遍布昆明全城的 100 家门店、四千地产经纪人是我们坚实的后盾。

    6 引用 • 141 回帖 • 548 关注
  • Hprose

    Hprose 是一款先进的轻量级、跨语言、跨平台、无侵入式、高性能动态远程对象调用引擎库。它不仅简单易用,而且功能强大。你无需专门学习,只需看上几眼,就能用它轻松构建分布式应用系统。

    9 引用 • 17 回帖 • 591 关注
  • 禅道

    禅道是一款国产的开源项目管理软件,她的核心管理思想基于敏捷方法 scrum,内置了产品管理和项目管理,同时又根据国内研发现状补充了测试管理、计划管理、发布管理、文档管理、事务管理等功能,在一个软件中就可以将软件研发中的需求、任务、bug、用例、计划、发布等要素有序的跟踪管理起来,完整地覆盖了项目管理的核心流程。

    5 引用 • 15 回帖 • 223 关注
  • 链书

    链书(Chainbook)是 B3log 开源社区提供的区块链纸质书交易平台,通过 B3T 实现共享激励与价值链。可将你的闲置书籍上架到链书,我们共同构建这个全新的交易平台,让闲置书籍继续发挥它的价值。

    链书社

    链书目前已经下线,也许以后还有计划重制上线。

    14 引用 • 257 回帖 • 2 关注
  • Openfire

    Openfire 是开源的、基于可拓展通讯和表示协议 (XMPP)、采用 Java 编程语言开发的实时协作服务器。Openfire 的效率很高,单台服务器可支持上万并发用户。

    6 引用 • 7 回帖 • 87 关注
  • IBM

    IBM(国际商业机器公司)或万国商业机器公司,简称 IBM(International Business Machines Corporation),总公司在纽约州阿蒙克市。1911 年托马斯·沃森创立于美国,是全球最大的信息技术和业务解决方案公司,拥有全球雇员 30 多万人,业务遍及 160 多个国家和地区。

    16 引用 • 53 回帖 • 104 关注
  • 京东

    京东是中国最大的自营式电商企业,2015 年第一季度在中国自营式 B2C 电商市场的占有率为 56.3%。2014 年 5 月,京东在美国纳斯达克证券交易所正式挂牌上市(股票代码:JD),是中国第一个成功赴美上市的大型综合型电商平台,与腾讯、百度等中国互联网巨头共同跻身全球前十大互联网公司排行榜。

    14 引用 • 102 回帖 • 405 关注
  • 又拍云

    又拍云是国内领先的 CDN 服务提供商,国家工信部认证通过的“可信云”,乌云众测平台认证的“安全云”,为移动时代的创业者提供新一代的 CDN 加速服务。

    21 引用 • 37 回帖 • 505 关注