[FOLIO-825] investigate Pact consumer-driven testing Created: 06/Sep/17  Updated: 17/Feb/21  Resolved: 17/Feb/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: Pact, ci, sprint22, sprint25, uitestingteam
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PDF File pact.pdf    
Issue links:
Relates
relates to UITEST-13 Investigate using Frontside (Karma ba... Closed
relates to FOLIO-630 Incorporate API-level integration tes... Closed
Sprint:
Development Team: Core: Platform

 Description   

Magda Zacharska would you please upload your slides here?



 Comments   
Comment by Magda Zacharska [ 06/Sep/17 ]

Here are the links to additional resources:
Pact documentation: https://docs.pact.io/
Pact-JavaScript version on github: https://github.com/pact-foundation/pact-js
Example of JavaSript project using Pact: https://github.com/DiUS/pact-workshop-js

Comment by Hongwei Ji [ 06/Sep/17 ]

I am thinking that Pact (Consumer-Driven Contracts) also helps to advance the version dependencies between Folio components. For example, one provider module introduced a break change and upgraded its major version, but that does not mean all consumer modules will break. Some might just be safe to move ahead to dependent on the latest provider if we have something like Pact to help to tell that. The end result is that we can have a leaner package/bundle and overall more current Folio ecosystem. Just a thought.

Comment by Matthew Jones [ 02/Oct/17 ]

There may be some overlap with UITEST-13 Closed (created in Montreal)

Generated at Thu Feb 08 23:08:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.