One of the most frequent questions we receive about Xmerge, Plastic SCMs built-in mergetool, is why the following merge scenario does not automatically resolve:

Over the last four months, part of the team was quite busy working on an evolution for the Plastic server.

We wanted to provide Enterprise Edition customers with a fault-tolerant, zero-downtime server for their on-premise setups.

This is the story of how we achieved it.

At Plastic, we strive to deliver the most bleeding edge version control technology across the multiple packages we maintain. That means anyone using Plastic in any platform with any interface will enjoy all of Plastic's goodies always.

In this post, we would like to summarize what have been the latest changes and updates to our CLI tool.

Michael Coté, host of some of the best podcasts on Digital Transformation, Cloud-based software development and other topics, interviewed Pablo Santos, founder and CTO of Plastic SCM. The conversation was, as the self-explanatory title reads, fun. This is a brief summary of it.

We take pride in many things: delivering an innovative product and changing the version control landscape one task at a time is one of them, for example; keeping together the same team since day one; growing year by year our client and user base...

If there is, though, one common trend to all those things it's that everything we do, we do with passion. We put our hearts and souls on what we do. Plastic SCM is thought and designed to enable its users to take their skills to another level. It is architectured to seamlessly integrate in your toolset and help you craft code. Be it because our users start using task branches, or because they are able to coordinate distributed teams without friction or, finally, because they implemented some automation in their DevOps pipelines.

Whatever it may be, they will eventually require help. Because version control is not easy.

Psst Gluon (picture from Commit Strip, September 12th 2017)

Wait... What? Is that Octocat?

Is Plastic SCM version 8 a new GitHub product? No!! This is our small homage to our dear colleagues at GitHub.

Plastic SCM version 8 is out and we wanted to play around with Octocat and our own Owl mascot. We have named it circumstantially and just for today, Octowl.

We've been busy lately and despite the holidays season taking away half of our team during the first week of January, we have been able to release some goodies and fix some buggies ;-) You can always refer to our publicly available Release Notes section in our site.

In this post, you find a briefly narrated, clear explanation of what has been released during this month.

We are happy to announce the release of GuiTestSharp, an open source GUI-test framework used to automate the testing of desktop apps written in C# on Windows, Linux and macOS.

As far as we know, it might be the first cross-platform GUI testing framework for .NET/Mono/Xamarin.

You can see it in action here:

And grab the source code now from its GitHub repository

We've been using this framework internally for years with success to test our Windows Forms, GtkSharp, Xamarin.Mac and WPF applications.

The framework itself is quite thin, and you simply have to fill a number of "test interfaces" to actually make your app testable.

This blogpost and the GitHub repository are the starting points to show you how to best use it and start GUI testing your C# applications.

We'd really like to find other teams who find it as useful as we do!