Hello all, I would like to have your many cents on test types (http://wiki.meego.com/Quality/Test_areas_and_types) and align these with the current types in test xmls (located in gitorius).
Vote, contribute, share your ideas on this. What could we change and where the change could happen? Following test types are listed in http://testplans.meego.com/handset-ux-tests/: - Functional - has definition in http://wiki.meego.com/Quality/Test_areas_and_types - I18N - not defined - Are the tests under this checking something like this: "Internalization (accuracy) testing: Testing adherence to the specified or implied internalization related (functional) requirements"? - L10N - not defined - I suppose definition could be something like this: "Localization (suitability) testing: Evaluating and validating the appropriateness of UI features from the perspective of linguistic and regional aspects for its intended specified tasks. This testing is based on localized user scenarios." - N/A - 169/702 ~ 24% of test cases do not have test type defined - could we have a bug against tests? - Non -Functional - I suppose all cases here are performance related - so I'm suggesting the type in xml(s) to be changed to "Performance" or one of the (sub-) types under that. - SystemIntegration - not defined in wiki today - could this be something like: "Tests whether a given group components and applications can function correctly in intended target vertical. Testing for integration may, for example, focus on ability of the software to automatically detect the communications needs of the systems it interacts with and switch accordingly."? o For Development Testing (a.k.a. Developer Testing by definition is [ISTQB Glossary] "Formal or informal testing conducted during the implementation of a component or system, usually in the development environment by developers") this has slightly different flavor: ยง (Component) Integration test - Introducing dependencies on external modules or data also turns unit tests into integration tests. If one module misbehaves in a chain of interrelated modules, it is not so immediately clear where to look for the cause of the failure. Tests are checking readymade part of the developer's product (implemented tasks and user stories) with simulators (stubs, test drivers) for missing external dependencies. - UserExperience - not defined in wiki today - Could someone suggest the definition for this? On Core OS area test plans we are having the following types in test plans http://testplans.meego.com/mcts/: - Non Functional - only one case on this category - should be moved to Performance or Reliability based on the target for test case - Benchmark - Defined in wiki - Certification - Defined in wiki - FUTE - 17 Cases - could be "moved" to Functional - Framerate - Defined in wiki - Functional - Defined in wiki - ITER - 2 test cases - could be "moved" to Iterative - Iterative - Defined in wiki - LATE - 4 test cases - could be "moved" to Latency - Latency - Defined in wiki - Long-lasting - Defined in wiki - Low-resource - Defined in wiki - N/A - 245/2373 ~ 10% of test cases do not have test type defined - Throughput - Defined in wiki Br, Jari [ISTQB Glossary] - http://istqb.org/download/attachments/2326555/ISTQB+Glossary+of+Testing+Terms+2+1.pdf
_______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
