Testacular (now Karma) is awesome, so is angular-scenario. Using them together is proving a challenge however. There is an ANGULAR-SCENARIO-ADAPTER in Testacular, but that b
The reason true becomes undefined is that you are using angular-scenario's version of expect (not Jasmine's version) which takes a parameter called future that will evaluate to a page element or property once the page has loaded.
Angular-scenario expects the future parameter to be an object with a value property. So when you pass in true it attempts to access true.value which evaluates to undefined.
expect({value: true}).toEqual(true); works fine.
You can't mix the 2 in one testacular configuration. What you should do is to prepare 2 distinct testacular configurations: one for running unit tests and another one for running e2e tests.
Then, you would run testacular twice: firstly to execute unit tests and then e2e tests. Usually I'm running unit tests very, very frequently (on each save!) while e2e tests just before a commmit (since those test run longer). We want to have the fastest possible feedback from unit tests while e2e tests are providing the ultimate safety net and assuring that parts of applications hard to cover with unit tests (navigation, UI etc.) are still working correctly.
This is the technique that AngularJS seed is using, you can see the corresponding definitions here: https://github.com/angular/angular-seed/tree/master/config