Installation issues

Closed:

5 | Active:

1 (0 in Test) |

things making the install less then optimal

Automated client-side testing

Closed:

0 | Active:

1 (0 in Test) |

Set up automated test infrastructure using Selenium. The result should allow us to automatically test a FileSender version on a number of browsers. We want to make sure FileSender works for a set of specific browser - browser version - OS - OS version combinations: the supported browser matrix.

The supported browser matrix should list those environments typically encountered in the wild. The only way to scale up testing to the number of browsers is by automating. The goal is to prevent help desk calls to people running FileSender installs.

Automated testing enables us to test all versions at any time: nightly builds, betas, release candidates.

Under development version 1.5

Closed:

14 | Active:

0 (0 in Test) |

Project infrastructure

Closed:

6 | Active:

5 (0 in Test) |

Stuff related to Assembla, sites etc. goes here.

Suggested features

Closed:

19 | Active:

41 (0 in Test) |

Placeholder for new feature suggestions. Features go from "Suggested features" to "Planned features" if they are to be implemented.

Workplan 2011

Closed:

0 | Active:

2 (0 in Test) |

temporary placeholder for the stuff in the workplan for 2011. Once we have prioritised the stuff here and the "smaller" tickets that were already planned or suggested, all stuff we work on goes into "planned" and "under development" as appropriate