Project

General

Profile

Actions

coordination #64126

open

[qe-core][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite

Added by tjyrinki_suse about 4 years ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

There's both 1) potentially indirect testing of packages that could be marked as tested automatically, and 2) database of TEST_SUITE_SUFFICIENT information from Updates Squad that could be used likewise.

Let's use this ticket to define guidelines for us.

How

  • How to own our testing better (Where our needs for tooling end, and where the tooling should be provided by external teams)
  • How to decide whether it should be a package test, an openQA test, or a separate test ran within openQA
  • How to match this with our test plan

Subtasks 2 (2 open0 closed)

coordination #88684: [qe-core][epic][qem] Identify packages that we are indirectly testingFeedback

Actions
action #88687: [qe-tools] Use the TEST_SUITE_SUFFICIENT value to mark packages as automatically testedNew

Actions

Related issues 1 (0 open1 closed)

Related to openQA Project - action #34486: database of "test cases" or how to search for tests we have in openQAResolvedlivdywan2018-04-08

Actions
Actions #1

Updated by okurz almost 4 years ago

  • Related to action #34486: database of "test cases" or how to search for tests we have in openQA added
Actions #2

Updated by tjyrinki_suse almost 4 years ago

  • Status changed from New to Workable
Actions #3

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [qam] Identify packages that have automated indirect testing or that have sufficient build time test suite to [qe-core][qam] Identify packages that have automated indirect testing or that have sufficient build time test suite
Actions #4

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [qe-core][qam] Identify packages that have automated indirect testing or that have sufficient build time test suite to [qe-core][qem] Identify packages that have automated indirect testing or that have sufficient build time test suite
Actions #5

Updated by tjyrinki_suse about 3 years ago

  • Tracker changed from action to coordination
Actions #6

Updated by tjyrinki_suse about 3 years ago

  • Subject changed from [qe-core][qem] Identify packages that have automated indirect testing or that have sufficient build time test suite to [qe-core][qem][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite
  • Status changed from Workable to New
Actions #7

Updated by tjyrinki_suse about 3 years ago

  • Subject changed from [qe-core][qem][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite to [qem][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite
Actions #8

Updated by tjyrinki_suse about 3 years ago

  • Description updated (diff)
Actions #9

Updated by szarate about 3 years ago

  • Description updated (diff)

Let's use this ticket to define guidelines for us.

  • How to own our testing better (Where our needs for tooling end, and where the tooling should be provided by external teams)
  • How to decide whether it should be a package test, an openQA test, or a separate test ran within openQA
  • How to match this with our test plan
Actions #10

Updated by szarate about 1 year ago

  • Tags set to platform-team
  • Project changed from 119 to openQA Tests
  • Subject changed from [qem][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite to [qe-core][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite
Actions #11

Updated by okurz 10 months ago

  • Category set to Enhancement to existing tests
Actions

Also available in: Atom PDF