You need to know what's on the cutting-edge of technology. Find out what's coming and the unique Warptest POV with just one click on the "Blog" tile.

All posts tagged ALM

The Microsoft GitHub Acquisition Is Official …

The Microsoft GitHub purchase is happening. The story leaked before the weekend onto the interwebs and by Monday June 5th, Microsoft and GitHub came clean with their official announcements.

The real loser in all this strangely enough was Apple whose annual WWDC event was fighting for attention online against the pro and anti-acquisition groups. GitHub and their competitor GitLab are more than just collaborative source control. Both have been adding features over the last few years including issue tracking, stories and other features evolving these tools into ALM solutions.

Why would anyone be against Microsoft acquiring GitHub?

After asking this question online, the only coherent, meaningful or logical argument I got was nothing to do with Microsoft and everything to do with any tech giant acquiring one of the most popular collaborative source-code tools on the market. To be fair, no-one should be surprised by this:

Microsoft GitHub - Reasons to be happy

Microsoft had been heavily invested in Git for several years, making it a fundamental option for working in Visual Studio. Meanwhile, everything about the Microsoft GitHub purchase is about mutual benefit but more importantly, increasing value for the Developer Community.

The two other reasons I got out of developers, startup founders, Devops and other were: –

  1. It’s Microsoft. I don’t trust them.
  2. Look at the acquisitions Microsoft ruined.

The counter argument to these were simple; what’s not to trust. Since Satya Nadella took over Microsoft, the company has radically changed. Look at the acquisitions since Satya Nadella took over as CEO. These companies have flourished and grown as part of Microsoft and so have their products e.g. LinkedIn.

If you really want to deep dive the reasons why Microsoft is a totally different company and its context vis a vis GitHub then you can check my video on it:

On the one hand, those against the acquisition are really stuck in the past. On the other, it’s a free market and you can vote with your feet. Tamir Gefen, CEO of ALMToolbox pointed out that this has happened with a major migration to competitor GitLab, who haven’t been shy about pushing how and why you can make the jump. He points to live online graphs of a large upturn in migration onto GitLab from their Grafana:

The graphs show migrations but don’t show some important metrics like: size of repositories, number of accounts moved and from what price bracket these migrations occurred. If the bulk of these are individual developers or people who opted for free accounts then the impact to GitHub will be marginal, other than the bandwidth and API calls being used in these migrations.

The Warptest POV

The Microsoft GitHub acquisition serves to highlight the strategy of Satya Nadella’s Microsoft. This is a break away from the Ballmer era. Microsoft is the biggest Open Source contributor in the world today (including projects like GIT VFS). Microsoft contributes to many projects like Electron and you only really need look at the Microsoft GitHub account to understand the scale of investment in developer hours that led to this purchase being a logical step.

Microsoft’s own online user documentation is held on GitHub repositories. Meanwhile Redmond continues to build more cross-platform apps for mobile than anyone else. They can do this because Visual Studio supports development in most, if not all platforms. Which lead us to other successful acquisitions that were logical steps to bring us this place;the purchase of Xamarin and HockeyApp.

Xamarin has flourished with Microsoft and their former CEO, Nat Friedman will takeover running GitHub following the purchase. HockeyApp has been rebranded and rebuilt by Microsoft as Visual Studio App Center.

This slideshow requires JavaScript.

Microsoft is fully aware that they need to earn our trust, even if the days of Vista are over. BUILD 2017 and 2018 showed us that Satya Nadella has placed the Developer Community, in its entirety front and center. Microsoft is a company that listens and continues to innovate, by purchasing companies and technologies that add value for their employees and end users. GitHub was also in talks with Google but at the end of the day opted to move forward with Microsoft.

For what it’s worth. if you don’t have to jump ship from GitHub, then my advice is to be patient and you will see why Microsoft and Satya Nadella have already earned our trust.

One final thought, if Microsoft now has Xamarin, HockeyApp and GitHub. What impact is this going to have on Visual Studio TFS in the future?

Microsoft GitHub - Keep Calm

Whatever happens. Keep calm and carry on Git Pushing.

What Can Twitter Possibly Teach Testers?

When working with testers who are still learning (all of us, right?), one of the challenges is finding a common language between testers and with Developers. This came up today and sparked this post:

This is especially important when it comes to writing test cases and reporting bugs.

In an age of “You had me at …” it’s crucial to get the point across rapidly and efficiently without compromising the information.

So.. Twitter Huh?

Twitter with its 140 character restriction on tweets is a natural teaching tool for anyone who needs to learn the discipline of brevity.

Twitter logo - testers

The thing is when reporting a bug it’s important to remember that you are imparting a story; a story that allows the Developer to know what should be fixed and under what scenario(s).

Imagine an ALM that was built on Twitter functionality: –

  • User stories, spec, test cases and bug reports all limited to 140 characters
  • Hashtags to make all of the above searchable by keywords.
  • Groups and Lists based on teams (e.g. QA, Dev, Product, Sales) and team members with usernames prefixed by the Twitter @.
  • Retweet, favorite or Direct Message (DM) other users.
  • Attachable images and URL shortening.
  • Trending subjects based on traffic within the ALM.
  • Analytics (of course).

The Warptest POV

As you read this keep one eye on the Agile Manifesto and see how Twitter Teaches Testers in an Agile manner. If you don’t see it, then it’s time to reread the manifesto:

agile manifesto - testers

The beauty of this method is not just the brevity but the rapid manner that it allows your testing to progress as everyone gets onboard with this manner of communication.

Obviously, there are exceptions, intricate or complex issues that require greater detail but the rule of thumb is,

“If you can’t sum up your bug or test case in 140 characters then it might be more than one issue.”

Does this speak to you? Feel free to offer your own experiences and ideas on the subject.