A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Soaring
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Is it time to stop adding features to soaring software? Is it timeto focus on reliability?



 
 
Thread Tools Display Modes
  #1  
Old December 11th 12, 01:01 PM posted to rec.aviation.soaring
pcool
external usenet poster
 
Posts: 69
Default Is it time to stop adding features to soaring software? Is it time to focus on reliability?

We have 500 unit tests, Max. FIVE-HUNDREDS.
We have a precise alpha and beta phases, scheduling a software delivery
after 10-12 months, only when 500 people are quite confident everything is
ok.
Is it enough to have 500 people doing this work?
I ask because personally I dont trust unit tests, for a simple reason: they
are made to report only if a desired result is obtained or not.
And the real truth is that for most of all functions you cannot check all
"desired results" and thus you are not accomplishing any real auto test.

The reason LK was created is that I was going to spend more time discussing
things with you, than doing them by myself and my own.

I am not going to comment the ridicolous statements by software
manufacturers that dont have innovations in their products, and call this
lack of innovations "desire of simplicity" (De vulpe et uva).



paolo





"Max Kellermann" wrote in message
...

On Tuesday, December 11, 2012 1:53:16 AM UTC+1, son_of_flubber wrote:
An open source software project like XCSoar is in a good position to do
this, because the developers are only paid in kudos, glory, and
self-satisfaction. (There is no revenue stream to maintain). There are
proven techniques for finding hidden defects, for example 1)Code
inspection 2)Functional testing 3)Exhaustive model-based automated
testing.


As Roel already said, we have many unit tests already, but not enough, there
is never enough. Since the first day I joined the XCSoar project as a
developer, I have worked on separating out code to run in isolated unit
tests. (Which, by the way, was the very reason the LK8000 was created:
because the LK8000 developer thought this was a bad idea, and so he left
us - LK8000 still doesn't have a single unit test.)

You are welcome to inspect the XCSoar source code and write more unit tests.
We would very much like to see more manpower put into it. Not because we
think that XCSoar is in a bad shape; it's pretty stable and the code has
become quite good over the years. But with more manpower, we could do so
much more.

Don't talk about how others should or could do something, just do it
yourself. Join our IRC channel and talk to us:
http://www.xcsoar.org/discover/irc.html (#xcsoar on irc.freenode.net)

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Non-Stop Soaring Film Fest: Showcasing The Best Soaring Videos Kemp[_2_] Soaring 20 December 21st 11 09:25 AM
Stop FireFox From Broadcasting Time & Date - READ THIS! heirophant Piloting 4 February 7th 11 03:54 AM
Webbased software for managing time of takeoff and landings [email protected] Soaring 0 June 10th 08 02:14 PM
Cross Country the main focus of soaring? mat Redsell Soaring 77 October 18th 04 10:40 PM
Soaring Software Academy before SSA Convention Paul Remde Soaring 5 October 8th 04 03:59 AM


All times are GMT +1. The time now is 06:36 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.