Hey, I had to accomplish the same thing on the enterprise project I'm currently working on. The good news is that it's quite easy to accomplish that and make it scalable, which means no fit/xit etc..
Oh, nice approach with a custom config! Hadn't thought of that. I'm not about the scalability because this will require multiple configs for different purposes, am I right? Smart idea nonetheless! Thanks for sharing it.
Maybe I have used the word scalability with wrong connotation here. The goal for me was to execute only specific tests in specific module/submodules to save me some time in cases where I have a a of Jasmine tests.
Yes, you are right. To achieve this you need to add a little bit of additional configuration. Nonetheless it's all about the context we are working in :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey, I had to accomplish the same thing on the enterprise project I'm currently working on. The good news is that it's quite easy to accomplish that and make it scalable, which means no fit/xit etc..
You can find an example of custom Jasmine configuration used inside Angular at my blog here: allthingsangular.com/introduction-...
It can be used to specify (include/exclude) exact folders, components, services or anything you want to test
If you need any help with setup just ping me.
cheers
Oh, nice approach with a custom config! Hadn't thought of that. I'm not about the scalability because this will require multiple configs for different purposes, am I right? Smart idea nonetheless! Thanks for sharing it.
Maybe I have used the word scalability with wrong connotation here. The goal for me was to execute only specific tests in specific module/submodules to save me some time in cases where I have a a of Jasmine tests.
Yes, you are right. To achieve this you need to add a little bit of additional configuration. Nonetheless it's all about the context we are working in :)