Testing release 0.52

[Nazarah]

Environment: staging.apinf.io
OS: Windows 10
Browsers: Chrome (latest), Firefox (latest), IE10

[Nazarah]

Date: 11/12/2017
Started executing manual testcases on release 0.52
Chosen platform: Windows 10, Chrome
Testcase covered: upto Number 5
Reported issues: #3203, #3204, #3206, #3208, #3207, #3209, #3210, #3211, #3212, #3213

[Nazarah]

Date: 13/12/2017
Executed testcases: 6.9 - 8.8
Environment: windows 10, chrome, staging.apinf.io, vamos. apinf.io
reported issues: #3227, #3228, #3230

couldn't execute testcase related to fiware login when fields in fiware authorization have incorrect values.
Didn't test dashboard
Couldn't connect API to proxy, so test was suspended.

[Nazarah]

Date: 14/12/2017

Executed Testcases: 8.9 - 9.8
Environment: Windows 10, Chrome, staging.apinf.io, vamos.apinf.io
reported issue: #3236, #3240, #3241

Couldn't test connecting API profile to EMQ Proxy.
connecting to other proxy failed in apinf staging, but passed in vamos deployment.
Continued testing in Vamos because of stability

[Nazarah]

Date: 15/12/2017

Executed Testcases: 10.1 - 10.8
Issues reported: #3246

Windows 10, Chrome (latest), https://vamos.apinf.io

[Nazarah]

18.12.2017

Executed testcases: 11.1 - 12.22
Reported Issue: #3250

Windows 10, Chrome Latest, https://vamos.apinf.io (rlease 0.52)

[Nazarah]

19.12.2017

Finished testing using Chrome Browser in WIndows 10 OS with https://vamos.apinf.io (release 0.52)
Executed Testcases: 13.1 - 17
Reported issues: #3258, #3260

[Nazarah]

20.12.2017

Finished testing positive scenario using IE11 on windows 10 OS on 0.52 release deployed on https://vamos.apinf.io
Reported issues: #3282, #3281, #3280, #3278, #3276, #3274, #3273, #3272, #3271, #3270 , #3266, #3265, #3261

[Nazarah]

Testing in FF could not be possible because of time shortage.