324. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 10/4/2017 8:04:43 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

324.1 Files compared

#	Location	File	Last Modified
1	rdk.zip\rdk\product\tests\acceptance-tests\features.arch	F362_ManualTest_BackgroundPatientList.feature	Mon Aug 21 12:51:01 2017 UTC
2	rdk.zip\rdk\product\tests\acceptance-tests\features.arch	F362_ManualTest_BackgroundPatientList.feature	Wed Oct 4 11:36:20 2017 UTC

324.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	10	104
Changed	9	18
Inserted	0	0
Removed	0	0

324.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

324.4 Active regular expressions

No regular expressions were active.

324.5 Comparison detail

	1	# Team Eur opa
	2
	3	Feature: F 362 - Back ground Pat ient List Management Services (CDS)
	4
	5	@F362-2.1_ create @US 5049 @manu al
	6	Scenario: Patient li st can be created
	7	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	8	When client re quests to create a p atient lis t using po stman
	9	Then t he success ful respon se is rece ived
	10	And the patien t list is created
	11
	12	@F362-2.1_ read @US50 49 @manual
	13	Scenario: Patient li st can be read
	14	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	15	When c lient requ ests to ge t a patien t list usi ng postman
	16	Then t he success ful respon se is rece ived
	17	And the patien t list is displayed in the res ponse
	18	# For manual tes ting use b elow URI i n postman
	19	# https:// IP /resource/ patientlis t with GET
	20
	21	@F362-2.1_ delete @US 5049 @manu al
	22	Scenario: Patient li st can be deleted
	23	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	24	When c lient requ ests to de lete a pat ient list using post man
	25	Then t he success ful respon se is rece ived
	26	And the patien t list is deleted
	27
	28	@F362-2.2_ create_def @US5050 @ manual
	29	Scenario: Patient li st definit ion can be created
	30	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	31	When client re quests to create a p atient lis t definiti on using p ostman
	32	Then t he success ful respon se is rece ived
	33	And the patien t list def inition is created
	34
	35	@F362-2.2_ read_def @ US5050 @ma nual
	36	Scenario: Patient li st definit ion can be read
	37	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	38	When client re quests to get a pati ent list d efinition using post man
	39	Then t he success ful respon se is rece ived
	40	And the patien t list def inition is displayed in the re sponse
	41	# For manual tes ting use b elow URI i n postman
	42	# https:// IP /resource/ patientlis tdefinitio n with GET
	43
	44	@F362-2.2_ delete_def @US5050 @ manual
	45	Scenario: Patient li st definit ion can be deleted
	46	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	47	When client re quests to delete a p atient lis t definiti on using p ostman
	48	Then t he success ful respon se is rece ived
	49	And the patien t list def inition is deleted
	50
	51	@F362-4.1_ patientLis t @US5186 @manual
	52	Scenario: Patient li st definit ion can be copied
	53	Given a pa tient with pid " R E D A CTED ;164" has been synce d through the RDK AP I
	54	When c lient requ ests to co py patient list defi nition usi ng postman
	55	Then t he success ful respon se is rece ived
	56	And th e patient list defin ition is c opied
	57
	58
	59
	60
	61