You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Class https://github.com/goaop/framework/blob/2.x/tests/Go/Functional/BaseFunctionalTest.php should be based class for all functional test, which would improve our testing capability for coverage of various edge cases by simply reproducing other people setup.
In order to have this kind of support, BaseFunctionalTest class and front controller should be modified in order to allow us:
to define which configuration should be used for AspectKernel for each functional test. That will allow us to test various configuration possibilities, especially useful for those where exception should be thrown and exception message is important. DONE, see Feature/detecting inconsistent weaving #346
to define which aspects should be registered in AspectKernel for each functional test. That will speed up testing process, as well as provide us with some isolation. DONE, see Feature/detecting inconsistent weaving #346
to implement custom assertWeaved* methods which would setup base possibility to check weaving of generated, cached classes (of course, without loading, using AST). Partially done
Class
https://github.com/goaop/framework/blob/2.x/tests/Go/Functional/BaseFunctionalTest.phpshould be based class for all functional test, which would improve our testing capability for coverage of various edge cases by simply reproducing other people setup.In order to have this kind of support, BaseFunctionalTest class and front controller should be modified in order to allow us:
to define which configuration should be used for AspectKernel for each functional test. That will allow us to test various configuration possibilities, especially useful for those where exception should be thrown and exception message is important.DONE, see Feature/detecting inconsistent weaving #346to define which aspects should be registered in AspectKernel for each functional test. That will speed up testing process, as well as provide us with some isolation.DONE, see Feature/detecting inconsistent weaving #346assertWeaved*methods which would setup base possibility to check weaving of generated, cached classes (of course, without loading, using AST). Partially doneDONE Feature/detecting inconsistent weaving #346assertClassIsWoven($class)DONE Feature/detecting inconsistent weaving #346assertClassIsNotWoven($class)assertClassHasStaticMethodJoinPoint($class, $methodName, $joinPoint, $index = null)assertClassHasNotStaticMethodJoinPoint($class, $methodName, $joinPoint)assertClassHasMethodJoinPoint($class, $methodName, $joinPoint, $index = null)assertClassHasNotMethodJoinPoint($class, $methodName, $joinPoint)