[PDB-3505] (maint) Use a real scope object for terminus testing Created: 2017/05/08  Updated: 2017/06/15  Resolved: 2017/05/09

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 4.4.1, PDB 5.0.0

Type: Bug Priority: Normal
Reporter: gepetto-bot Assignee: Adrien Thebo
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by PDB-3507 (maint) Use a real scope object for t... Closed
relates to PDB-3498 Fix rspec resource-related failures w... Closed
relates to PDB-3498 Fix rspec resource-related failures w... Closed
Team: Systems Engineering
Story Points: 1
Sprint: PuppetDB 2017-05-31
Release Notes: Not Needed
QA Risk Assessment: Needs Assessment


Changes coming in Puppet 5.0.0 change how Puppet::Parser::Resource
instances set default values; in specific they do so upon object
construction which requires a functioning(ish) scope object. The
Puppetdb terminus specs were relying on the scope object being
relatively simple and easily stubbed but this change in defaults makes
it much harder to treat the scope object as an easily stubbed object.

To simplify stubbing and potentially reduce future breakage this commit
changes the scope stubbing to partially stub a full scope object instead
of creating a pure stub object and adding methods as necessary. By using
a full scope object we can let the internal APIs of Puppet handle
implementation changes.

Generated at Sat Jul 20 12:42:54 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.