[Monodevelop-devel] GSoC 2014. MonoDevelop
m.j.hutchinson at gmail.com
Wed Mar 5 18:06:00 UTC 2014
On 4 March 2014 12:51, Sergey Khabibullin <x2bool at gmail.com> wrote:
> Hello. My name is Sergey. I am a student at Moscow Technological Institute
> (formerly known as World Technological University UNESCO).
> I am looking forward for GSoC 2014.
> I know that proposal should be made later at offical Google Summer of Code
> site, but I was told that it would be better to contact with
> mentoring organisation earlier.
> I was around Mono since I moved my development activities from Windows to
> Linux. And I am happy that I haven't had to trade one of my favorite
> programming languages for something else.
> I studied Mono's project list for GSoC, but I want to propose something
> else. My target is MonoDevelop (Xamarin Studio), specifically an Xunit.net
> test runner. I was planning an addin for MonoDevelop since the past autumn,
> and I have studied for that purpose Mono.Addins, Xunit sources, NUnit addin
> and, of course, basics of MonoDevelop's internals.
> At this moment my only opensource activity is this little project
> (https://github.com/x2bool/NCaptcha/wiki). The project was written
> ~2 years ago, and it's not the best code humanity has ever written. However,
> the code does it's job.
> My hope is to make the Xunit addin that will copy (at least most of the
> parts) the functionality of the existing NUnit addin. I think it would be
> wise to target the Xunit 2.0 (now in beta) release. The Xunit.net itself
> doesn't seem to be the hardest part, but it will require some amount of
> code. I see the hardest challenge in GUI integration because I am not
> familiar with Gtk-Sharp. But if it's more or less like Java Swing or
> Android's GUI framework this shouldn't be impossible.
Yeah, GTK# isn't difficult to pick up.
That said, I don't think much (if any) GUI work is necessary to
integrate XUnit - the sensible way to do this would be to plug in
XUnit as a test provider/runner into the existing unit test addin.
There would be some work to finish abstracting out the NUnit
dependency from the existing addin - maybe even modeling this
abstraction on the VS2012 unit test runner interfaces
to make it easier to port over OSS unit test adaptors from VS.
> As I understand my chances will increase if I will do some work to show my
> skills. What should I do? Can I pick up a random bug from bugzilla, work on
> it and make a pull request?
Yep. Preferably something you're interested in. And feel free to ask
questions if you're not sure how to approach the bug :)
More information about the Monodevelop-devel-list