Skip to content
#

Continuous integration

Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

Here are 1,971 public repositories matching this topic...

nightwatch
Adrian-Tamas
Adrian-Tamas commented Dec 30, 2019

Describe the bug

The element annotations from the sections can't be used in the section commands although the documentation https://nightwatchjs.org/api/pageobject/ indicates that it should. They can however be used at the page object command level

Original discussion:
https://groups.google.com/d/msg/nightwatchjs/zMxy4P4GOWA/oXcna71uBAAJ

Sample test - using nightwatch-api + mocha + c

GaneshSPatil
GaneshSPatil commented Dec 19, 2019
Issue Type
  • Feature enhancement
Summary

GoCD application has a separate page to manage the different GoCD entities. Each page has either an Add or Create button to create a new entity.
The styles of these add entity buttons are different on each page. Example:

On Pipelines Page:

![Screen Shot 2019-12-19 at 11 34 41 AM](https://user-images.githubusercontent.com/152

jhfoo
jhfoo commented Jul 23, 2018

There's a list of deprecation warnings installing Strider. A sample as follows:

npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated mailcomposer@0.2.12: This project is unmaintained
npm WARN deprecated browserslist@1.4.0: Browserslist 2 could fail on re
fspegni
fspegni commented Dec 17, 2019

I cannot find any reference, in the documentation, about how the history of past builds is handled. Is it stored in memory? On files? On the database?

I'm running buildbot in docker (one container for the master, one for the worker, as in the "simple" scenario). Whenever I have to modify the master.cfg I have to

  • stop the master container
  • remove the master container
  • start again the mas
jx
cake
prezire
prezire commented Aug 22, 2017

The online WIKI says anyone can edit via GitHub. Is this safe and gets validated by anyone?

Expected behaviour

  • Detailed step by step instruction about the installation and setup.

Actual behaviour

  • Missing steps such as renaming of htaccess and configuration details such as phpci.yaml.
  • Location of phpci.yaml is not explicitly defined.
  • *Examples of directory and fi
werf
tox
lastbackend
Wikipedia
Wikipedia

Continuous integration apps

BuildPulse

Automatically track flaky builds. Measure improvement over time. Install in less than a minute. Works with your current CI

App Center

Continuously build, test, release, and monitor apps for every platform

Flaptastic

Manage flaky unit tests. Click a checkbox to instantly disable any test on all branches. Works with your current test suite

See more Continuous integration apps
You can’t perform that action at this time.