Difference between revisions of "User:Usul/testing"

From Navit's Wiki
Jump to: navigation, search
(Automated tests)
 
(2 intermediate revisions by the same user not shown)
Line 58: Line 58:
  
 
==Automated tests==
 
==Automated tests==
 +
We want unit tests and build servers for all platforms to monitor codecoverage, test passing and buildsuccess
 
*will make a lot of additional work
 
*will make a lot of additional work
 
*might be difficult as platforms might behave differently
 
*might be difficult as platforms might behave differently
Line 68: Line 69:
 
*->makes commiting/merging code less pain
 
*->makes commiting/merging code less pain
 
*https://sites.google.com/site/ruslancray/lab/projects/cunittestingframeworkswithcodecoveragemetrics/c-unit-testing
 
*https://sites.google.com/site/ruslancray/lab/projects/cunittestingframeworkswithcodecoveragemetrics/c-unit-testing
 +
 +
==Continuus integration==
 +
* Test before commit to mainline
 +
* need a server with jenkins CI, CUnit
 +
* need devs that start writing tests
  
 
==tests==
 
==tests==
 +
===UI===
 +
*different languages work ok?
 
===search===
 
===search===
 
*address
 
*address
 +
*in countries/languages
 
===routing===
 
===routing===
 
*10,50,100,400km routing
 
*10,50,100,400km routing
 +
*in countries/languages
 
==rendering==
 
==rendering==
 
*zoomout to continents
 
*zoomout to continents
 +
==devices==
 +
*div dev. classes (input/output/speed)
 +
*div. OSses (integration and compatibility)
  
 
[[Category:Development]]
 
[[Category:Development]]
 
[[Category:Testing]]
 
[[Category:Testing]]
 
[[Category:Ideas]]
 
[[Category:Ideas]]

Latest revision as of 18:29, 26 March 2014

we need

  • testcases
  • testpatterns
  • testprotocols
    • platform(ver)*device*tester*country
  • remaining bugs


How can we make sure, that we offer working fine crossplatform releases of our tool to the public and thus:

  • decrase need for support
  • increase user satisfaction
  • Show that navit is a reliable source for navigation

Very basic[edit]

  • Compiles every port?
  • All ressources are available for every port?

General[edit]

  • Installation/Update
  • Setup
  • Use
  • Deinstallation

platform indipendend[edit]

Does the most stuff work on the linux port?

platform dependend[edit]

Does all work on the single ports?

Basic[edit]

Here we test the essential functionality, that navit must offer to work as a navigation system.
Please use your consumer device and no simulation modules!

  • Is Navit starting?
  • Is first run displaying an map and OSD is enabled?
  • Is that map style complete and ok for your scenario?
  • Can you control navit with your device in a usual way?
  • Do you get GPS?

Usecases[edit]

  1. Check if you have an valid location and search for surrounding POIs
  2. Try to find your home/parents/holiday location (same city) and start routing
  3. Try to find a address a few miles away and start routing
  4. Plan a short route around your area and try to follow it

Report[edit]

  • GUI and OSD
  • Map style and handling
  • Interaction
  • TTS

Advanced[edit]

  • Try other GUIs and Graphics engines with the basic usecases


build tests[edit]

  • apply only commits, that don't break the build

Automated tests[edit]

We want unit tests and build servers for all platforms to monitor codecoverage, test passing and buildsuccess

  • will make a lot of additional work
  • might be difficult as platforms might behave differently

Continuus integration[edit]

  • Test before commit to mainline
  • need a server with jenkins CI, CUnit
  • need devs that start writing tests

tests[edit]

UI[edit]

  • different languages work ok?

search[edit]

  • address
  • in countries/languages

routing[edit]

  • 10,50,100,400km routing
  • in countries/languages

rendering[edit]

  • zoomout to continents

devices[edit]

  • div dev. classes (input/output/speed)
  • div. OSses (integration and compatibility)