Semantic MediaWiki

Hey,

We want to use the latest wmf version of MediaWiki as the base platform of
> our wiki. Is this a wise idea in your opinion or should we use the stable
> version?
>

These versions of MediaWiki tend to be pretty stable on themselves.
However, if you use them, you might end up running into compatibility
issues with the latest release of SMW. To avoid that, you could run the
latest code of SMW, which most of the time works fine with these WMF MW
versions, but running the latest SMW code (ie git master) can lead to
stability issues. I'm running the latest of both, and so is
translatewiki.net. It works as long as occasional breakage (which is
usually fixed pretty quickly) is acceptable to you.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--

Thanks Jeroen!

Speaking of tests - we've written a VERY big form that includes most
of the form elements we use in our projects and some more pages with
various result formats. Now when we update our software we can always
see what went wrong.
-----
Yury Katkov



On Tue, Aug 21, 2012 at 2:09 PM, Jeroen De Dauw <jeroendedauw@...> wrote:
> Hey,
>
>
>> We want to use the latest wmf version of MediaWiki as the base platform of
>> our wiki. Is this a wise idea in your opinion or should we use the stable
>> version?
>
>
> These versions of MediaWiki tend to be pretty stable on themselves. However,
> if you use them, you might end up running into compatibility issues with the
> latest release of SMW. To avoid that, you could run the latest code of SMW,
> which most of the time works fine with these WMF MW versions, but running
> the latest SMW code (ie git master) can lead to stability issues. I'm
> running the latest of both, and so is translatewiki.net. It works as long as
> occasional breakage (which is usually fixed pretty quickly) is acceptable to
> you.
>
> Cheers
>
> --
> Jeroen De Dauw
> http://www.bn2vs.com
> Don't panic. Don't be evil.
> --

Hey,

In an effort to increase quality of SMW (by reducing the amount of bugs)
and facilitating future development (by regression detection) I've been
adding unit tests to SMW. Not that many, but at least we now got some
coverage. Nischyan has also been added a bunch as part of his GSoC project.
And I'm now looking into getting a CI server up running these unit tests
and the Selenium tests Benedikt Kämpgen wrote over a year ago.

I encourage everyone concerned with the quality of SMW to contribute their
tests in a form that can be used by people working on the software. It's
nice if you spot regressions on your site between releases, but it's way
better to not have these regressions happen in the first place :)

If anyone has or questions on how to create them, I'd be happy to help you
getting them into SMW.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--

Hi Jeroen! I looked at some tests and I see that they are indeed
pretty easy to understand and write. I have a question now: how do you
fill the database for the tests and clean it up afterwards? Probably
we can contribute a little bit to SMW and semantic extensions writing
tests.

Still I see that non-unit tests are also useful: by creating mega-form
and super-page with all result formats we were able to detect many
problems in our extensions and bugs in our skin.

-----
Yury Katkov



On Thu, Aug 23, 2012 at 11:46 PM, Jeroen De Dauw <jeroendedauw@...> wrote:
> Hey,
>
> In an effort to increase quality of SMW (by reducing the amount of bugs) and
> facilitating future development (by regression detection) I've been adding
> unit tests to SMW. Not that many, but at least we now got some coverage.
> Nischyan has also been added a bunch as part of his GSoC project. And I'm
> now looking into getting a CI server up running these unit tests and the
> Selenium tests Benedikt Kämpgen wrote over a year ago.
>
> I encourage everyone concerned with the quality of SMW to contribute their
> tests in a form that can be used by people working on the software. It's
> nice if you spot regressions on your site between releases, but it's way
> better to not have these regressions happen in the first place :)
>
> If anyone has or questions on how to create them, I'd be happy to help you
> getting them into SMW.
>
>
> Cheers
>
> --
> Jeroen De Dauw
> http://www.bn2vs.com
> Don't panic. Don't be evil.
> --

Hi,

On Fri, Aug 24, 2012 at 2:42 AM, Yury Katkov <katkov.juriy@...> wrote:

> Hi Jeroen! I looked at some tests and I see that they are indeed
> pretty easy to understand and write. I have a question now: how do you
> fill the database for the tests and clean it up afterwards? Probably
> we can contribute a little bit to SMW and semantic extensions writing
> tests.
>
>
The unit tests create temporary tables themselves to work with, so no
cleanup required :)


> Still I see that non-unit tests are also useful: by creating mega-form
> and super-page with all result formats we were able to detect many
> problems in our extensions and bugs in our skin.
>
>
I agree non-unit tests are useful, but unit tests will catch bugs a lot
earlier.

-----
> Yury Katkov
>
>
>
> On Thu, Aug 23, 2012 at 11:46 PM, Jeroen De Dauw <jeroendedauw@...>
> wrote:
> > Hey,
> >
> > In an effort to increase quality of SMW (by reducing the amount of bugs)
> and
> > facilitating future development (by regression detection) I've been
> adding
> > unit tests to SMW. Not that many, but at least we now got some coverage.
> > Nischyan has also been added a bunch as part of his GSoC project. And I'm
> > now looking into getting a CI server up running these unit tests and the
> > Selenium tests Benedikt Kämpgen wrote over a year ago.
> >
> > I encourage everyone concerned with the quality of SMW to contribute
> their
> > tests in a form that can be used by people working on the software. It's
> > nice if you spot regressions on your site between releases, but it's way
> > better to not have these regressions happen in the first place :)
> >
> > If anyone has or questions on how to create them, I'd be happy to help
> you
> > getting them into SMW.
> >
> >
> > Cheers
> >
> > --
> > Jeroen De Dauw
> > http://www.bn2vs.com
> > Don't panic. Don't be evil.
> > --
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Semediawiki-devel mailing list
> Semediawiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>



-- 
Cheers,

Nischay Nahata
nischayn22.in

Hey,

> The unit tests create temporary tables themselves to work with, so no
cleanup required :)

This is indeed the case, as long as you indicate the tests to be in the
"Database" group using the "@group Database" annotation. Important to not
forget that :)

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--