Project

General

Profile

Bug #10281

Bug #8059: Windows Camouflage automated tests sometimes failed due to differently ordered icons in the notification area

Bug #7233: How to deal with tests expected to fail?

Document how we deal with tests expected to fail

Added by anonym about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
-
Category:
Test suite
Target version:
Start date:
09/26/2015
Due date:
% Done:

100%

Feature Branch:
kytv/feature/10281-expected-test-failures
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

Document the procedure mentioned #7233#note-26. Note that when #10198 is done, and the Suites feature has landed in in Cucumber, we will have a better way to implement this, so this procedure will just be a temporary solution until then.

Associated revisions

Revision 13a6948f (diff)
Added by anonym about 4 years ago

Document how to deal with tests expected to fail.

This is a temporary solution until we solve #7233 properly.

Will-fix: #10281
Refs: #7233

Revision a0b6e251
Added by intrigeri about 4 years ago

Merge remote-tracking branch 'kytv/feature/10281-expected-test-failures'

Closes: #10281, #7233

History

#1 Updated by anonym about 4 years ago

  • Parent task set to #7233

#2 Updated by anonym about 4 years ago

  • Related to Feature #10198: Wait for the cucumber Suites feature added

#4 Updated by intrigeri about 4 years ago

  • Related to deleted (Feature #10198: Wait for the cucumber Suites feature)

#5 Updated by anonym about 4 years ago

  • QA Check set to Dev Needed

#6 Updated by anonym about 4 years ago

  • Status changed from Confirmed to In Progress

#7 Updated by anonym about 4 years ago

  • Assignee changed from anonym to kytv
  • % Done changed from 0 to 50
  • QA Check changed from Dev Needed to Ready for QA
  • Feature Branch set to feature/10281-expected-test-failures

Does the instructions in commit 13a6948 make sense to you?

Just a thought: What about commenting out the scenarios instead of deleting them Git? We could also reference the ticket tracking them being disabled. That should make it harder to forget about disabled scenarios, and easier to fix them if step name's changes (i.e. we alter the commented out version and deal with the trivial conflict resolution when reverting).

#8 Updated by kytv about 4 years ago

  • Assignee changed from kytv to intrigeri

#9 Updated by intrigeri about 4 years ago

  • Assignee changed from intrigeri to kytv

Just reassigning to me doesn't communicate very clearly what review you've done (if any). Please clarify :)

#10 Updated by intrigeri about 4 years ago

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_1.7 to Tails_1.8

Postponing and thus raising priority a bit.

#11 Updated by kytv about 4 years ago

  • Assignee changed from kytv to intrigeri
  • Feature Branch changed from feature/10281-expected-test-failures to kytv/feature/10281-expected-test-failures

Sorry, I reviewed the steps defined and those were good. Rereading tonight I spotted typos that for whatever reason I missed the first time. I corrected these and I pushed them to my branch.

#12 Updated by intrigeri about 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

#13 Updated by intrigeri about 4 years ago

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Also available in: Atom PDF