You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Frictionless developmentMinimize developer toil with self-service access to fast, secure workflows and GitHub-style actions running on Tekton. Faster and saferDeliver software faster with built-in security and compliance checks at every stage of development and deployment. Continuously improvedBe your best with constant feedback loops across the entire software delivery value stream - no more inte
After two fantastic years in Munich with SinnerSchrader, I’m back in San Francisco and started my shiny new job at Buoyant as VP…
In this second iOS TDD howto video, Robert van Loghem from Xebia Mobile, shows you how to setup Jenkins Continous Integration Server to run GHUnit unit tests which were developed in XCode 4 and committed in git. This is an integral part of doing Test Driven Development for iOS (iPhone, iPod touch and iPad)
Post published:January 31, 2010 Post Author:Christian Hedin Post Category:Agile / Testing Post Comments:32 Comments Continuos Integration is the practice of integrating changes from many people as often as possible. Instead of merging changes once a month and spending time handling merge errors you try integrate every day, perhaps even every hour. Each integration is built and tested on a server.
Continuous Integration Continuous Integration (CI) has been around for a while now. Popularized in the java/ruby/[lang] communities, CI, when properly implemented promotes good code practices. CI alone won't guarantee great code, but it helps support good behavior and in fact rewards users routinely and reliably. I've used Continuous Integration in many former lives - CI was essential on large ge
はじめに 今回は、Jenkins と Python の連携についてです。 使用するツールは、とても便利なテストフレームワーク nose と カバレッジ coverage との連携についてです。 nose連携 まず、 nose との連携からです。 nose をそのまま実行したのでは、Jenkinsに取り込めないため、XUnit形式のレポートを出力する必要があります。 XUnit形式のレポート出力には、 unittest-xml-reporting を導入する必要があります。 unittest-xml-reporting がインストールされていると、noseの出力レポートをXUnit形式にすることができます。 インストール $ easy_install -ZU nose $ easy_install -ZU unittest-xml-reportingnose の使い方は割愛しますが、コマンド
準備 PHPUnit実行時に必要になるxdebugをインストールする。 Hudsonに次のプラグインをインストールする。 Hudson Phing Plugin Clover Plugin xUnit Plugin build.xmlの作成 <?xml version="1.0" encoding="utf-8" ?> <project name="StringUtil" basedir="." default="test"> <target name="clean"> <delete dir="reports" includeemptydirs="true" /> </target> <target name="test" depends="clean"> <mkdir dir="reports/coverage" /> <exec dir="." command="phpunit --
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く