lower but out of my name is strictly less than I am the the maintainer for tuning the members the fault testing framework Over the last year which is a lot of new stuff and unit including punitive out which we that a lot of how we approached thinking about the testing but 1 of the most frequent questions I still get is that folks as the like why is it so hard using no the right used you node I will today I had the pleasure of announcing for the 1st time ever the arrival of Tunisia the a new tool that makes tinnitus doesn't know just as easy as it is in the browser so you don't have to do any more on salt the parties of MPM packages so this means that since q unit is installed by default to embassy alive you now consider test not just for your browser code because if we would build were server code just as easily without any additional installs so this he lies in the early stages of the 1 which have to bear in this stuff for most common use cases this includes filed lobbying so that we don't have to like passing recursive flags and can explicitly decide which test to running the filtering which is very power by 2 units of the existing delta function so that we can do things like inverse filter is a rejects filters customer orders which I'll talk about more in a moment so I watching rapid development and iteration and seated randomizations are you can try to catch sleepy tests of as is already done Indian the example so we planted on this quickly and a feedback would be tremendously appreciated to get started with this I have to do is impairments thought unit globally the and probably ones you know so we can see how exactly do users the along with the CLI we've been shipping other features as well including unit to do so this is a new type of tasks that we've introduced alongside skid tests in the normal way testimony and the idea is that to do tests represent features that are fully implemented yet in your code base so they expect to have at least 1 failing assertion war 1 here from within an but they're still be reported as OK by the test reports this way when you have finished implementing the future and that test is passing all the way will be reported as not OK and you know it actually enable this as the real testable regressions in the future the so in a sense this should become the bedrock avidity TDD workflow and this is something that is then asked for many times and in the community especially as we undergo large we've factors for things like glamor so additionally when you use these tests of honesty I will give you feedback about like not just how the test

02:59

itself will but whether task to fail but also like exactly what is wrong with the taxi and track that state along with the new type of task we added a bunch of insertions add to it and the most excited about what we refer to as the step PPI and he's very simply to track the execution flow of protest as aggressors so asserts that takes any true value to use as a tag for individual portions of the task and you can then call verify steps to verify the water and the occurrence of those tax so together user super useful and highly asynchronous systems my user interfaces for any promise this library or even a testing framework with venues news events so the strategy I also allows you to easily verified on make different parts of the system as the test is executing and allows you to replace things like special counters the boolean 5 so you might have previously used to do testing of the sort of things that are semantically meaningful feedback lastly we recently adopted the JS reporters standard for logging callbacks so this reporters as standard specifying events and their payloads for test frameworks but that

04:21

reporters Convention June it is the 1st framework to adopt this standard but we have been in contact with other big testament such as Jasminum OK to try to get them on board as well and there's lots of interest in this area the idea is that eventually you no longer have the specific framework coxless unit began in instead of a common interface of and on function an event and there you can specify the standard event names and the call that so you provide to them will receive standard errors this makes it easy to write a reporter once and then shared amongst all testing framework so that regardless of the specific implementation so things like track reporters or . reporters you know I have to write 1 per framework you can just write it once and I know that it works well and then use it in anything that you adopt but so to that and that this

05:17

allows us to easily create custom reporters Fortuna now and all you have to do is defining him packages the have just

05:24

reporter as a key word it and then import the functions that are exported there and use them from the command line really easily these losses in the browser and you can look at the unit documentation to see how to do that and so that's what's new and you are in solution and I really encourage you to check out the COI especially if you are an amount of in diversity feedback so we can work with the eyes to make it thanks you