Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests are failing on version 1.0.7 #36

Closed
MantasVaitkunas opened this issue Mar 27, 2018 · 10 comments
Closed

Tests are failing on version 1.0.7 #36

MantasVaitkunas opened this issue Mar 27, 2018 · 10 comments
Assignees

Comments

@MantasVaitkunas
Copy link
Contributor

I tried to run tests with module v1.0.7 and OXID eShop compilation v6.0.1 and got some failures:

vendor/bin/runtests
1) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__fcpoHandlePaypalExpressUser_RemoveAddressFromSession
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_fcPayOneUser_3756d52c)
2) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__fcpoHandlePaypalExpressUser_CreatePaypalDelAddress
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_fcPayOneUser_3756d52c)
3) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__fcpoHandlePaypalExpressUser_ThrowException
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_fcPayOneUser_3756d52c)
4) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__fcpoHandlePaypalExpressUser_CreatePaypalAddress
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_fcPayOneUser_3756d52c)
5) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__handlePayPalExpressCall_Coverage
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_DeliverySet_612589a8)
@PirxDanford
Copy link
Contributor

PirxDanford commented May 4, 2018

Hi, additionally to the above Errors there was also one Failure:

1) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__fcpoDoesPaypalUserAlreadyExist_Coverage
Failed asserting that false matches expected 'someUserId'.

Is there any progress on this issue?

@fjbender
Copy link
Contributor

fjbender commented May 7, 2018

Not yet, we're still working on this.

@PirxDanford
Copy link
Contributor

Hi, as our regular maintenance release (eShop compilation v6.0.3) is coming up end of July it would be very good if we could bump up from using v1.0.5. Any progress?

@fjbender
Copy link
Contributor

fjbender commented Jun 8, 2018

Can you confirm that the tests pass with #38 merged? Then I'll bump up the version.

@fjbender
Copy link
Contributor

Version bump will follow once #39 is merged.

@fjbender fjbender assigned fjbender and hreinberger and unassigned andrefatchip Jun 12, 2018
@PirxDanford
Copy link
Contributor

Hi,
sadly with 1.0.8 we still see this one error:

1) Unit_fcPayOne_Extend_Application_Controllers_fcPayOneOrderView::test__handlePayPalExpressCall_Coverage
OxidEsales\Eshop\Core\Exception\SystemComponentException: Function 'fcpoDoesUserAlreadyExist' does not exist or is not accessible! (Mock_DeliverySet_e958571e)

and one failure is new:

1) Unit_fcPayOne_Extend_Application_Controllers_fcPayOnePaymentView::test_fcpoGetPayolutionAgreementLink_Coverage
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'https://payment.payolution.com/payolution-payment/infoport/dataprivacydeclaration?mId=&lang=someAbbr&territory=DE'
+'https://payment.payolution.com/payolution-payment/infoport/dataprivacydeclaration?mId=c29tZUNvbXBhbnk=&lang=someAbbr&territory=DE'

We might have a solution for the error, if so I'll make sure a pull request is provided. For the failure please have a look at how to solve this and if it is sufficient to provide the changed URL in the test.

@PirxDanford
Copy link
Contributor

We now have provided a pull request (#42). As this is only about test coverage we still can take v1.0.8 for the next release, so no need to hurry.

@fjbender
Copy link
Contributor

Thanks, we'll review

@PirxDanford
Copy link
Contributor

Just noticed this has not been closed yet - thanks for taking the pull request :-)

@hreinberger
Copy link
Contributor

Thanks for the notice (and the PR of course)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants