A number of findings from 2013 were re-confirmed including the frequency of application deployment and lower failure rates found amongst high-performing organizations. However, I thoroughly enjoyed the additional questions that support the statement that IT is not just a cost center, it's a source of profitability, an opportunity for greater market share and a threat to the competition.
Continuous Integration and Continuous Delivery are both earmarked as best practices that correlate most strongly to high IT performance. You can read the entire report yourself here but here are some findings that stuck out to me:
- "IT performance and well-know DevOps practices, such as those that enable continuous delivery, are predictive of organizational performance."
- "It’s not dev versus ops, it’s dev plus ops. When the outcome of a dev and ops interaction is win-win, IT performance wins."
- "Companies with high IT performance are twice as likely to exceed their profitability, market share and productivity goals."
- "Developers breaking large features into small incremental changes and merging their code daily into trunk are strongly correlated with both IT and organizational performance."
- "Continuous improvement and learning is what sets successful companies apart, enabling them to innovate, get ahead of the competition — and win."
Marketing Funnel Manager
Follow her on Twitter
The team is proud to announce the release of SonarQube 5.0, which includes many new features
- Issues page redesign
- Keyboard shortcuts added to Issues
- Built-in SCM support
With this version of the SonarQube platform, the Issues page has had a complete overhaul.
Issues are grouped in the list by file, and from the list of issues, you can easily navigate to the issue in the context of the code, as you’re used to seeing it,
Issue search has also been overhauled. You can still choose from criteria, but now next to each facet of the criteria, you see a count of the relevant issues.
Selected facets are highlighted in blue, and selecting/deselecting a facet immediately (okay, there’s a quick trip to the server and back) updates your search results and the issue counts next to all the other facets.Keyboard shortcuts added to Issues
The intent behind the redesign is to allow you to use the Issues page quickly and efficiently to manage issues on a daily basis. To that end, extensive effort has gone into providing a broad set of keyboard short cuts. ‘?’ brings up the list, and Esc closes it.
From the list of issues, right-arrow takes you to the issue-in-context, and left-arrow takes you back to the list. In either context, up-arrow/down-arrow takes you to the next issue – in the same file or the next one – and you can use the shortcuts to comment, assign…Built-in SCM support
SCM “blame” information has been an important data point in the SonarQube interface for a long time, but until now a plugin was required to use it. Now SCM data comes as part of the platform, with built-in support for SVN and Git.
Speaking of Git, its rise in popularity has meant that the use of ‘/’ in branch names has become increasingly common. Until now, that was unsupported by SonarQube. That changes with 5.0, presumably making many Git-ers happy. :-)That’s all, Folks!
Time now to download the new version and try it out. But don’t forget that you’ll need Java 7 to run this version of the platform (you can still analyse Java 6 code), and don’t forget to read the installation or upgrade guide.
These by far are the highest distinction a uTester can receive, and are a celebration our top community members of 2014 — for their dedication to quality, helping others in our community, commitment to uTest projects, and excellence in authored content on the uTest site.
Winners will receive a custom uTester of the Year t-shirt and prize pack, and their names will be forever enshrined in our uTest Hall of Fame. We also have a couple of tricks up our sleeve for this edition — we’ll be launching our first-ever Lifetime Achievement Award!
While our Project Managers, Community Managers (and for the first time ever, Test Team Leads) are already busily voting away behind the scenes, we’re happy once again to bring back the Community Choice Award so our uTesters have their say in the process. We’re looking to our community to nominate their rockstar peers for their work in 2014!
If you are already a uTester, get your vote in for the Community Choice Award category for this year’s awards by Friday, Feb. 6. Also, stay tuned for the announcement of the winner, along with all uTesters of the Year for 2014, in our full announcement on Feb. 18.
In Part I of this blog I explained which metrics on the Web Server, App Server and Host allow me to figure out how healthy the system and application environment is: Busy vs. Idle Threads, Throughput, CPU, Memory, et. Cetera. In Part II, I focus on the set of metrics captured from within the application […]
The post Key Performance Metrics For Load Tests Beyond Response Time- Part II appeared first on Dynatrace APM Blog.
This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office.
You have just finished refactoring some code without modifying its behavior. Then you run the tests before committing and… a bunch of unit tests are failing. While fixing the tests, you get a sense that you are wasting time by mechanically applying the same transformation to many tests. Maybe you introduced a parameter in a method, and now must update 100 callers of that method in tests to pass an empty string.
What does it look like to write tests mechanically? Here is an absurd but obvious way:
// Production code:
def abs(i: Int)
return (i < 0) ? i * -1 : i
// Test code:
for (line: String in File(prod_source).read_lines())
1: assert line.content equals def abs(i: Int)
2: assert line.content equals return (i < 0) ? i * -1 : i
That test is clearly not useful: it contains an exact copy of the code under test and acts like a checksum. A correct or incorrect program is equally likely to pass a test that is a derivative of the code under test. No one is really writing tests like that, but how different is it from this next example?
// Production code:
def process(w: Work)
// Test code:
part1 = mock(FirstPart)
part2 = mock(SecondPart)
w = Work()
It is tempting to write a test like this because it requires little thought and will run quickly. This is a change-detector test—it is a transformation of the same information in the code under test—and it breaks in response to any change to the production code, without verifying correct behavior of either the original or modified production code.
Change detectors provide negative value, since the tests do not catch any defects, and the added maintenance cost slows down development. These tests should be re-written or deleted.
The Jenkins User Conference 2015 is seeking submissions that reflect the latest innovations in Jenkins usage. This is your chance to educate, share and inspire the community with stories of how you've used Jenkins to continuously build that amazing project or how you developed that popular plugin that everyone is using.
If you're gamed, here are some suggestions to get your creative juice going:
- Scaling Jenkins within the enterprise
- Jenkins as the orchestrator for continuous delivery
- Plug-in development
- Jenkins techniques that solve testing/building problems in specific application areas: mobile, enterprise/web/cloud and UI testing
- War stories that speak to a problem you faced, the Jenkins solution you implemented to solve it and the results you realized
- Jenkins best practices, tips and tricks
- Jenkins in the cloud - if you or your company is currently using Jenkins in the cloud we’d love to hear your story
- Beyond Java (Jenkins with PHP, Ruby, etc.)
We are upping the ante at this year's JUCs. We are moving from a 1 day conference to a 2 days conference for SF and London - that's 18 additional cutting edge sessions to be learned.
There's also a wide variety of event sponsorship opportunities available. There are offerings from Gold to Silver packages, exhibitor packages in our world-class expo hall, speaking sessions, free passes, and many branding opportunities. For inquiries, pls contact firstname.lastname@example.org
Looking forward to receiving your amazing proposals!
In tomorrow's Jenkins office hours, Jesse Glick will talk about two topics in the workflow plugin that he has been asked about:
- Security model: script security, permissions
- Plugin compatibility: SimpleBuildStep and friends, custom steps, etc.
The session should be interesting to anyone using workflow or thinking about using workflow. Jesse is one of the top contributors in the community, so it'd be definitely worth your time!
LoadRunner 12.02 includes a technical preview of the newly-designed, browser-based Web Controller. While defined as a technical preview and therefore not including all the existing Controller’s features, this version is fully functional and supports defining and running load tests with a variety of popular protocols such as Web, TruClient, SAP GUI and Citrix.
Continue reading for an introduction to the new Web Controller’s capabilities.
(This post was written by Shaul Strachan from the LoadRunner R&D Team)
What happens when production releases go from an all-day Saturday event requiring a small army to a push-button 5 minute process? More velocity, happier customers, and a team that can see their families on the weekend.
When failing one in a million times is too much, and continuous delivery is critical.
We’ve mentioned before that testers and QA engineers have some of the most job satisfaction out of anyone employed. Now, this already happy bunch may have something to be even happier about.
According to a recent report by Fortune Magazine based on data from job-seeking site Indeed, software quality assurance engineers and testers ranked no. 7 on its list of the top 10 most in-demand jobs for 2015.
It’s really a testament to just how hot the mobile app space is right now — and the burgeoning wearables and Internet of Things markets. As you’ll notice from the list below, testing is the only job here that is tech-skewed.
There’s bound to be plenty of opportunities to go around if testers want to make the switch in 2015, with companies itching to get their apps perfected in the hands of their users.
Check out the full report from Fortune Magazine, and the complete list here of the top 10 jobs for the new year.
Top 10 In-Demand Jobs (2015):
- Registered nurses
- Truck drivers
- Customer service representatives
- Sales managers
- Sales representatives
- First-line supervisors or managers of retail sales workers
- Software quality assurance engineers and testers
- General and operations managers
- Managers (all other)
- Accountants and auditors
This transformation is forcing companies to adapt the way they think about IT processes, how business differentiation gets created and pushed to market. Rather than long 18 to 24-month release cycles where risk is high and value creation sparse, companies are moving towards "Continuous Delivery" (aka CD), where business value is continuously pushed to market, in small iterations and measured to see whether it yields expected results. This not only hugely reduces risk (large projects, time to market, etc.) but makes it possible to react to market changes and competitive moves much faster.
Adopting Continuous Delivery involves many changes within an organization. And ultimately, it implies to have a way to automate the process that starts with value creation (i.e. new software) down to its actual release, going through sophisticated automated build, tests, integrations, staging, validations, etc. The more automated a pipeline gets, the more code-release-measure iterations are possible in a give timeframe and the more value can be pushed to market. Automation is king.
CloudBees is offering the #1 solution on the market to implement enterprise Continuous Delivery at scale, based on the open source Jenkins CI project. With the rapid adoption of Continuous Delivery within organisations, CloudBees went through spectacular growth in 2014. This being just the tip of the CD-iceberg, we decided to gives ourselves the means to to achieve our objectives. Consequently, today we are announcing a US $23.5m capital expansion, led by Lightspeed Venture Partners, including follow-on investment from Matrix Partners, Verizon Ventures and Blue Cloud Ventures.
This investment will make it possible for us to further SCALE-UP and SCALE-OUT.
SCALE-UP as we further invest in our go-to-market to help more and more companies around the globe successfully adopt Continuous Delivery at scale.
SCALE-OUT as we expand the type of use cases and deployment types our solution supports so we can help an even wider range of companies to benefit from Continuous Delivery.
We will be making a lot of announcements in the next weeks and months, so stay tuned.
"Ranorex is pleased to work with GlobalNow as our first preferred partner in LATAM and as an affiliate partner in the US. GlobalNow's testing services center in Costa Rica, reach in Latin America, and Spanish language support enhances Ranorex's ability to support the significant opportunity in Latin America as well as the US. We believe this collaboration will enhance our offering to our clients and better address their testing challenges," states Robert Muehlfellner, President of Ranorex North America.
"We are very excited to align with Ranorex as a preferred partner. As part of our testing service offering, we were keen on finding the "best" cross platform test automation solution available in the market. After much analysis, we selected Ranorex based on its ease of use, cross platform coverage (web, mobile, tablets, etc.), test execution methods, high level of customer support and overall affordability. Including Ranorex as a component of our testing offering enables our clients to realize maximum return from their test automation initiatives" explains Bob Foster, CEO and founder of GlobalNow, the motivation for partnering with Ranorex.
GlobalNow, headquartered in Dallas Texas U.S., is a software development and software quality assurance company with global teams located in multiple Latin America locations, including our software testing center located in San Jose, Costa Rica. Our quality assurance service focuses on the testing of applications and systems by applying best in class tools (such as Ranorex), with affordable QA engineers and proven operational methods; reducing our client's cost while improving their customer satisfaction and overall service quality.
For more information about GlobalNow, please visit http://globalnowit.com/costa-rica/
To read more, visit our blog at blog.sonatype.com.
According to the TestFlight website:
The services offered at TestFlightApp.com will no longer be available after February 26, 2015. To prepare for the TestFlightapp.com closure, developers and team leaders are recommended to transfer their testers to the all-new TestFlight Beta Testing in iTunes Connect.
TestFlight is a free service that allows developers to test apps that have not yet been published on the App Store. Apple acquired the mobile platform just over a year ago, so the news that it’s being rolled into Apple’s portfolio doesn’t come as a huge surprise, but nonetheless could have implications for testers.
Testers — what’s your reaction to the news? We’d love to hear your feedback in the comments below.