#7115 closed change (rejected)

Explicitly test expiration parsing

Reported by: ukacar Assignee:
Priority: Unknown Milestone:
Module: Core Keywords: closed-in-favor-of-gitlab
Cc: erikvold, rscott, jsonesen Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):


We were looking at the tests in the synchronizer.js file and could not find any explicit tests for the expiration special comment parsing.

Change History (4)

comment:1 Changed 21 months ago by rscott

  • Cc rscott added

comment:2 Changed 17 months ago by mjethani

Could you please describe in a little more detail what exactly we should be testing here? It would be nice to have an example or two.

comment:3 Changed 17 months ago by mjethani

  • Cc jsonesen added

comment:4 Changed 12 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.