• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Namespaced Tests

Has anyone experimented with namespacing tests in third-party packages? Like if I made a library and Jill includes it with `composer require mgatner/libfoo`, and I want to supply tests for the user to verify functionality, ensure stability, work with pipelines, etc... Do I provide a Tests folder they would need to copy into somewhere? Or can they run the namespaced tests right out of /vendor with CI4’s tests and PHPUnit?

Looking into this for a developer on the slack channel. Will share my findings once resolved.

There’s a Slack channel? Is that public?
(And thanks!)

It is in the composer.json file, for sure. I suspect other places, too ... might have to beef that up.

“Don't have an account on this workspace yet?
Contact the workspace administrator for an invitation”


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

Users browsing this thread:
1 Guest(s)

  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.