I don't know any things while I walk by night. I don't know any strange tales hidden in the hearts of men and women who have stepped into the shadows. Yes, I know the nameless tales of which they dare not speak. My friend's blood, it's the whistler's strange story, right boy. So inwardly he was waving at her, outside Steve Carson, the core of the piece of ice. Ten years of the private detective and woman of mass, the manchalance outside in spite of the burn-ups underneath. Yes, Steve was a top-notch detective, a bright boy, smart enough to see when Werner came along five years ago that investigation fees were chicken fees, but with her beauty and his ability, there was real money on the other side of the line in blackmail. It turned out to be a great point, an unbeatable combination, and as he left the automatic elevator at the end of the corridor and walked down to her apartment, he felt what a shame it was that Werner could be so naive as to think she could change it with a simple phone call. Well, that is easy. We've been expecting you. I could tell by your attitude on the telephone that you were unhappy, dear. You know Randy Summers, of course. Lord Mr. Carson, nice to be to drop in. Then I want to talk to you alone. Good morning, Uncle. Well, my darling, good to see you. Of course. Looks like you can use one. Are you going to get that guy out of here? No. I like having him around. Do you think it'll be a whole still for this? I think so. Well, that's a bad guess. If he stays, I go. Are we going through all that again? I'm not playing second horn, baby. You want to lose students, that's your business. If I'm going to quit, that's mine. I'm a private eye, not an airboy. Would you rather I put it down and writing? And writing? Dear fellow, surely we should know by now whether to put on anything and writing with two friends or not. Yeah, that is, Summers. I'm afraid I'll miss the class and it won't be the least of the class that it's not easy, darling. What do you think, old man? No, see here, Carson. I can take so much of your back. Hey, stop it! God, let's see him! Now, look. I told you once before how things stand, man and I are running the show from now on and we'll let you know what we need you. Is that clear? Okay, Grunner. This is you around. Meaning there might be others? Good boy. What about our dear friend Charles W. Ralston? Who's ever to tell him about the letters? What? Well, you wouldn't stoop to that and I'll leave you. I suppose Ralston, of course, he found out he'd been paying for letters a few months ago. What? What children? What if it is? What happened? A little fire, son. It's an accident that there was cannon. Well, she kept the letters there. Oh, the place at the Glade Tower. Wasn't it the one Ralston built for you as a contribution to the cause? Yes. Well, nice, darling, wasn't it to you? Oh, you love it, Landy. No. Niles from anywhere. It was nothing to do with the time, so it wasn't a total loss. You know, Steve, I think I'll have that O-Sauce and Ceiling wrap removed. It's too dangerous. It's only going to happen again. What about the place, Grunner? What about the letters?  What makes you think I won't? Well, let's see.  We know how death was an accidental, don't we, Steve? And then there's that swindler on the falcon woman. And there's a few other indicators you wouldn't want to be able to know about. A skeleton in the father and just the other scarlet, huh?  And I know how you feel about short hair cuts. No, darling. I don't think you're going to tell Mr. Ralston anything. You're going to go right under him with a favor for me without the usual percentage. You do it best for him. There you go. All the time, Steve. You knew me. Well, that's it. Go ahead, then. You knew me. It's very touching, darling. I have no idea, Mr. Castleman, so sentimental. What do you think, Grunner? Come on, let's have a drink, Grunner. Oh, I mean, at this time, old man, shall we try not to spill it? It's also a good scarlet. Please. Oh, now, Steve, there's a few other things I'd like to discuss with you. I'll be flying down to Los Angeles tonight when it gets back to your drawing with the carbon. The cannon? Going up alone in my afternoon. Why don't you drop by a good coxing, Grunner? Well, I don't know, Grunner. You think you're out of good? Not me, Grunner. Well, I could let you know in the morning. Good. You do like to stand, don't you? That land, Grunner. Everything's going to work out all right. All right, boy. Minding us to know there's only one way to handle Grunner now. Leave him in an apartment.  I don't think you know me, Mr. Rolston. I'm afraid I do. Steve Carson's probably investigated. I came to see you about a misplaced shelterman. I'm sorry, I don't... I have a composition, Mr. Rolston. Nasty, huh? Yes, we do. You know all about the letters, of course. Mr. Rolston, you're a pretty influential businessman in this city. And shall we say, not without enemies. You know, let's suppose this shelterman's letters would have fallen into the hands of the wrong people. She's assured me they will if you don't know her. Suppose she would have sold those letters to a group of individuals who are so much quoted that you could afford to pay. She wouldn't fold, but she would and is. They haven't been able to find out that much in a little more. Shall I go on? She's going to a cabin tomorrow. Over the weekend, someone will contact her there to meet the transaction. They ought to work fast if you want those letters. I see. What's your proposition? I think I can break up that little meeting before it ever takes place. You could get the letters for me? Yes. But my fee is one little high for this sort of thing. And how much, Carson? $25,000. I can't possibly get it. You don't think it's worth it? No, I couldn't, Carson. $25,000. Think it over. And do make up your mind soon, Lawson. I'll call you sometime tomorrow morning. You're quite certain she's planning to sell those letters? So quite certain. How do I know that this isn't another one of her tricks? And how do I know you're not in weaver? That's just a chance you have to take, Mr. Lawson. Good night. The next move is a big one, isn't it, Steve? There's a matter of the defective kerosene lamp in Burnett's cabin at Lake Tahoe. It's the same lamp that caused the fire that burned Mr. Lawson's letters. A few nights later, it's liable to happen again, isn't it? Especially since you arrived at the cabin five hours later, equipped with five gallons of high-test gasoline, and pretend to change the possibility. Either with certainty. You can see Burnett now arriving at the cabin, pulling the lamp down. There's a flash of a match, an explosion, and a fire to remove any trace of your visit. By eight o'clock the following morning, we're back in town to call on Burnett, your promise, to regress that you can't accompany her, and to make sure her visit to the cabin is coming off on schedule. He said, isn't it bright, boy? Oh, yes. I'm standing by. The lieutenant's just left on an errand. Oh, yeah? What are you? Come on, Sergeant. What's the pitch? What are the police doing here? I was just going to ask you what you're doing here. Of course you'll tell me first, huh? I was calling in Burnett. Business. Mm-hmm. There, if you want it. Who's there? Under the blanket. He's dead. In this case of homicide, a blunt instrument to corner free. Surprise, please? In just a minute, the workflow will continue tonight's story. All of us are part of our hometowns and rightly so. In this brief moment before we continue with our program, we'd like to offer a link to one of our hometowns in America, Indianapolis, Indiana. Top of the state and the Great Transportation Center, Indianapolis extensive trade is based on the rich territory that surrounds it, large coal fields, tremendous deposits of building stone, and one of the richest sections of corn and wheat in the world. But perhaps one of the best known features of the city to the world at large is the Indianapolis Speedway. It was built in 1909 as a proving ground for automobiles, and each memorial day, the famous 500-mile race is held there. From the experience gained in this annual event, have come many improvements in automobiles. Every time you use your rear-view mirror, every time you trade your tank with F-O-F-E, every time you appreciated the comfort of your improved tires, you were given credit to something that was first used on that Speedway. Indianapolis has its famous citizens, too. Benjamin Harrison, the 23rd president of the United States, called it his hometown. So did James Hickson Riley, the great leisure poet, and it was the birthplace of General Walter Beiber Smith, chief of staff of the American forces in Europe during World War II. Nearly half a million people live in Indianapolis today, and no charge of the parts of home town is played in the building of America. And now back to the thriftler. Stop too cold, isn't it, Steve? The news of Werner's murder.  Everything was figured out, planned for us, like a stone trap. Everything's gone. Werner's dead, yes. You're the number one suspect. And you're driving on a lonely mountain road, and I'm telling you, can't explain that the moment she was killed. That'll sound great, of course, isn't it? But there's one thing you assure us. Waltzden killed her. There's no question about it. We talked last night. The deadline you crossed up to him. It was Walston, all right. It takes you just 15 minutes to get across town for a showdown, but we'll get right to the point, Walston. I'm here for two reasons. The first is that I'm sure you'll not go to Werner's showings if I've been there watching you. What? No, don't look surprised, Walston. I had nothing to do with it. Don't give me that. I didn't get in front of any of the junk in the entrance hall, and I could see them going over with a fine-tooth comb. Maybe some are looking for those letters, eh? Somebody figured, tomorrow, I might be too late. Why are you so interested? My good friend, Sergeant LaHara, seems to think I killed it. Unfortunately, it looks like my only defense is to prove you did it. Letters unless... Uh, unless what? Unless I can deal with an alibi. I'm with Caleb, Walston. I've been in the business long enough to know what all I've got to do to hand you is to crush those letters in the DA's office. You have them? I know where to get them. I've got them, Walston. I'll do anything. I'll do anything. First, there are a few things I'd like to know. When did we see you at Turner's apartment last night? I didn't go to her apartment last night. Okay. I'm gonna dig up those letters. You are, Walston. Wait a minute. I did it. Yes. I did it. I did it. I did it. I did it better. Now, you wouldn't have just hopped a cab and gone over there to Macaroon, Walston. No, no, you're smarter than that. You must have been moved somewhere else at the time. Mm-hmm. First time. I went down to the Yacht Harbor. I have a boat back. What time? Ten fifty. No one saw me first for a short time after I went overboard the boat. We came by and called off the base of the dock. We had seen the life of the boat. What time? Ten thirty. We talked to it? Yes. So as far as he was concerned, we were on the boat between ten sixty and eighteen. We didn't see the gale until I'd come back the second time. Not until I had asked him when he saw it burning. What time? Eleven thirty. No. I couldn't have done much better myself, Walston. I was lucky. I spoke to the watchman at eleven thirty when I was leaving for the night. Anyway, that's a new... Yes. Several men, a few yards away. I don't know. I think they came from the club. Okay. And the watchman was a caller. I don't know. I spoke to him. I suppose so. You have a dog, but I... I think you must have noticed. Oh, that's good enough for me. I'm sure the police will accept your word. What are you doing there? You're my other eye. I was with you in that boat all the time. Remember? Whoa! That alibi was a lot to me, Walston. Might even be willing to forget about the twenty-five thousand. The watchman didn't see me when I was in the boat in New Orleans. He didn't see me when I went to find his apartment. Me when he came back. And when I finally checked with him, just before going home, there were others around. That makes a lot of sense for the both of us. What about the others? You know I'm fine, Walston. There were almost 20 pieces and you couldn't find them. I could have told you they weren't there.  Yes? The same way that she did. Don't trust me, do you? Listen, Tom. Bring the roses. And I'll give you the cash tonight. I'll wait until the investigation's over. It's safer that way. For Stevie? See, it looks like she's been on a poker game. You're looking back now, watching each of them throw their trump cards. Knowing all the time you have to topple up your fleet. One day summer, the beautiful will be on a rollback to my family. And you know in a few seconds after he finishes his story of what happened between you and Werner on the evening of the motor, the duo will be on the phone, asking for the answers. There's nothing to do now, but wait. Third day. Friday. And then Saturday morning you should enter your office. Hello, guys, boy. I've been waiting for you. It's on your mind, though, Anna.  You and my shouting band are good friends, aren't you? Particularly good friends. For what? A little shower.  Look at that to you. Did you know I slept in there because she dropped you for the summer's guy? You ought to start disagreeing. That's all. The first floor was a wicked door to her apartment. The second was the next door in a downtown bar, and don't say you didn't because summer's so cold, so does the bartender. The third one was on the night she was killed, just after she called you on the phone and told you it was all off. What was the beef about? Well, you wouldn't be interested. Summer's was her too, incidentally. He was still holding on to her. He caught the man 40 times playing at the airport. We checked him. Now you were there at 7.30. Yes, the first time. What do you mean, the first time? You didn't go back around 10.30? What are you talking about, O'Haz? Things to shout and go and let a phone call at me in 15 was the first thing he was left. It was from you? Uh, well, the minute you are wrong. You made an appointment to see her at 10.30. That's all right. Summer's been giving her eyes. Summer's was there when the call came in. She told him it was you. But you were coming back. Summer's wanted to stick around in case he got rough, but she told him she could handle you. So he took his plane. The guy trying to have it. I believe him, Constance. That's how I tend to have this warrant. In the great debate of 1787 and 88, as to whether the Constitution should be voted for or against, the framers of our Constitution had a hard fight on their hands. They also had many allies. And one of them was James Sullivan, who wrote the following words to the Massachusetts Gazette in November of 1787. Let us view the characters who composed the late Constitutional Convention. Are they not men who, from their infancy, have been nurtured in the principles of liberty and taught to pay a sacred regard to the rights of human nature?  Gredlin and citizens listen to the voice of men who have thought only of you and your posterity is good. The Constitution was voted for, of course, because it was understood that the men who framed it did so not only for themselves, but for the future. We today are that future. And now back to the whistlers. It's quite a poker hand, isn't it? O'Hara and Summers have played their cards, but you still have the copper up your sleeve. However, the phone call Verna supposedly received from you was puzzling, isn't it? You tried to figure it out as you sit in the atty room, waiting to see District Attorney Skellig. Summers must have been telling the truth. For some reason or other, Verna didn't want him to know who called and told him it was you. It was Ralston, of course, pleading for his letters again.  Ralston, you knew you'd need that top car, didn't you, Steve? But you had no idea you'd need it this badly. Well, cousin? Hello, dear. Doesn't look so good, does it? Yeah, got it all figured out, huh? Just about. Oh, good. Now if you'll stop figuring long enough to ask me where I was at the time of the murder, maybe we'll all have a great big laugh. Okay. For sure. I was on a boat at Yacht Harbor talking over some confidential business with a client of mine. Yeah? Who? He's a pretty important guy, Skellig. Big shot in the savings alone business. I suppose his name's confidential, too. No, no, not at all. Charles W. Ralston. Is that good enough? Ralston? If you don't believe me, get on the phone. Call him. You're, uh, serious about this? Sure. Can you call him up? You better brace yourself. Ralston was killed in a cabin at Lake Tahoe last night. Seems a coal oil lamp exploded or something. A couple rangers saw the flames. Something wrong, cousin? Now a question. Do you know when the naval rank of Commodore was first recognized as such? During the Revolutionary War, the Navy used the rank of Commodore simply as an honorary title. Until 1861, all Navy captains who had at any time commanded a squadron were considered Commodore, though they were never actually given that commission. In 1862, however, Commodore was established as a fixed rank, and in July of that year, 18 were commissioned on the active list and 17 on the retired list. This is but one of many interesting facts which can be found in the history of your United States Navy. Oh, boy! He did it in tonight's transplant story. We'll build four minutes of this list. The Whistler, Jack Moyle, Betty Lou Derson, Jack Edward, Victor Rodman, Vic Tarran, and Olin Soule. The Whistler, directed by Gordon T. Hughes with music by Wilbur Hatch, is produced by Joel Malone and transmitted overseas by the Armed Forces Radio Service. This evening's story was by Adrian John Doe. The Whistler was entirely fictional and all characters portrayed on the Whistler are also fictional. Any similarities of names or resemblances to persons living or dead is purely coincidental. This is George Walsh speaking, reminding you to listen again next week for another spring tale by The Whistler. This is the United States Armed Forces Radio and Television Service.


Hello my dear crafty friends, this is Eva. If you are new here, I am journal maker and I love to create lots of pockets and some funny stuff in my journals and today I'm gonna show you how you can create this beautiful movable pop-up page in your journal and if you would like to learn more about pop-up things, pop-up pages, pop-up cards I do have for you YouTube channel where from I am learning all my skills with pop-up pages with pop-up mechanism. It's the pop-up channel and Mr Duncan Birmingham, he's explaining everything really well. He does have amazing tutorials and he does have so many tutorials for any kind of pop-up pages, pop-up mechanisms. So link will be down below, go to have a look go to Lin, it's awesome. For all of you who will be interested in this design, we do have here little journal, little rent book and we do have here note card, we do have pocket. So all these designs you can find on my Etsy link will be down below. I hope you will enjoy this tutorial. We do have this design, there are four pages from rent book, no this is from saving book actually and here we do have a rent book cover. I do have ink bottle and hand and this will be movable part so I'm gonna fussy cut out. I did print out this design on A4 size cardstock 160 gsm. It's not too heavy but it's heavy enough to hold the shape and I do believe it's heavy enough to hold also that movable part. Both designs, this design will be in both sizes US letter size and A4 size. So find the size you are printing on usually and print on. I'm gonna fussy cut out all these images and I do have here this journal and I choose, I hope I'm gonna kind of place it right here so I'm gonna keep it here. I'm gonna fussy cut out all these images and we will glue it together. I do have all my images fussy cut out so now I'm gonna move to cutting part. Here on this movable part you can see this little rectangle so I'm gonna be using ruler and knife and I'm gonna cut this top line. Then on these dots, dots lines I'm gonna be using stills pen and I'm gonna just emboss these lines to make sure that I can fold it easily and I'm gonna also do same on the edges of this image. Now I can fold everything and also fold the inside of that triangle and then it should be folded this way. So once again you will get up that triangle, push it down and with your fingers press this and the opposite side and then it will navigate you to fold the triangle down below. Use bone folder and burnish all these folds. This little part will be glued here on one side of that on right side of that triangle but before I will do so I like to add a little bit of shade to my images so I'm gonna be using distress ink. I'm gonna be using this seal brown from spectrum noir harmony line and I'm gonna distress edges on all my images to add there a little bit of shade. This will be probably all hidden but you know just in case and I'm gonna add a little bit of that seal brown to bottom on opposite side of my images as well. I did fussy cut out all my images with a little bit of white print around to make it more easy for me and give them nice shape and full image and now I can kind of hide that white paper with this distress ink so it will be not that much visible and I would like to add also a little bit of ripped edges to my papers so I'm gonna be using scissors and with the edge of my scissors I'm gonna rip off a little bit distress, a little bit the edges of my little pages and as vintage pages they do have worn edges kind of thinner edges and then it's middle of the paper so I'm gonna be using my nail file and I'm gonna sand specially corners and here and there are also the parts of the paper itself. I'm gonna take this small piece and I'm gonna add the glue to the right side here to that triangle take this piece and place it in there be careful do not place it to that fold and do not place it over the edge here just in the middle and let it dry meanwhile I'm gonna sewn little book from these pieces so I'm gonna place my book pages in the middle of this little journal and I think I'm gonna use just two, two of them and two of them I'm gonna keep as decoration for the journal so I'm gonna place them in the middle and sew them as this would be proper journal and I'm gonna make a knot from outside this time so very easy sewing make a knot I'm gonna keep these here for now just gonna cut them similar and I hope we are ready to assemble all this to a journal so I'm gonna open my journal where I would like to give this go I'm gonna get a pencil and this size from this fold this size I'm gonna make a mark on this page so from here till here it's somewhere here gonna make a mark and now I'm gonna put the glue here on the edge of my foldable piece somewhere here I would like to have my moving mechanism so I'm gonna glue it there now I'm gonna put the glue here fold your piece this way put the glue on this white fold place it down close your book wait until it's dry and when you when you open your book it will lay flat down so play with it let it dry properly before you will open your book and now it's time to assemble everything you have here so you will need to find the right position for the hand put the glue here and place the hand right there then the ink will go under and I think here I'm gonna put a little bit of card stock underneath and with that card stock the bottle will be a little bit pop up so I'm gonna place it right here I can try oh come on fold inside yeah those first foldings you will need to help to your mechanism don't be afraid to push it with your hand okay and now about the rent book which will hold our hand slightly down so I can glue that rent book on this part I can't go over this triangle so I'm gonna use this page put the glue here grab my journal and with that page I'm gonna place it in there I can go over this edge here and I'm gonna let it dry so I think this is dry I'm gonna also put a little bit of glue here in this corner right here because that corner will be free the in this image will go here behind this part so here I can put the glue and I'm gonna glue there one page as well it will hold the hand down and it will kind of navigate the hand how it's supposed to fold and now these two I can just lay down around my image and do some kind of you know layer I supposed to I think I should glue it under this one I'm gonna unglue it use my two pages create a little layout here so first this one and over that this one fold it and now I can put back the bottle and then when you open and close your book the hand is going for ink so I hope you did enjoy this one we do have a little journal right here we do have a little writing spot here and also also there is a little pocket right here so that's all my sharing for today you will find all these images on my Etsy shop link will be down below for all my patreons no matter in which year they are the link the link the images are for download in yesterday post I hope you did enjoy this this video I hope you had some idea what you can create in your journal thank you so much for visiting me today thank you so much for spending your time with me have a wonderful day take care of yourself and I will see you soon bye


And today's agenda is mobile element inspectors. So what kind of inspectors do we have in market now and how it is going to evolve in future? And next is need for speed. How we are going to run our automation scripts much faster than now, we are now. And next is handling multiple simulators at a time, wearables or TVOS support. Inspectors that we develop for wearables and TVOS, how an automation tool is going to support those apps and next is star driven enterprise and it is not mobile first now, it is AI first. So we will go there from how we are now. So have you used any inspectors, can be in mobile or it can be in a web, name any? Anything which we have used? Any inspector tools? Have you giveaways, those who are quite interactive? Yep, anything? Anything for web? We have plenty of add-ons, sorry? Firebug? Yep, pretty cool. Firebug, Firefinder and lot more from Chrome and Firefox add-ons, that is for web. And anything for mobile? Have you used any web inspectors, mobile inspectors? Bit more specific? Yeah, and there are a lot of mobile inspectors currently in market. We have one from Google, which is a UA Automata viewer, which is used to inspect our mobile apps to get the hierarchy and find the IDs or any properties of the mobile elements. And next we have from Facebook, we have one tool called WebDriver Inspector. So group of Facebook techies have developed WebDriver Inspector to inspect iOS apps, especially for iOS 10 and plus. And next, there is another inspector, which is pretty cool. Makaka JS, it's from Alibaba team. So they have developed an inspector to inspect mobile element properties on both Android and iOS, which wasn't before, like Android's UA Automata viewer doesn't inspect elements in a mobile apps of iOS platform and Facebook's WebDriver Inspector for iOS is not possible to inspect mobile elements in Android apps. So Makaka came up with a concept to fulfill these gaps, automate inspect elements in both Android platform and also in iOS platform, that is apps in both the platforms. So, but still there is a limitation, which doesn't render properties for few elements, which is in a UA Automation Platform or UA Automation Library, which is a pretty old library, which aptly deprecated couple of years back. And next is another inspector, which is still in development, that is APM desktop inspector. So it suffices all the needs, like it supports both the platforms, that is apps developed in Android and iOS both, and it has integrated with APM server and pretty cool GUI for now. It's still in a development phase, it suffices all the needs of a mobile inspector, and this is how it looks. We have an app, Odca app, developed internally in ThoughtWorks, so this is how the GUI looks. So we have the properties over here, I think it's not quite clear, it's okay. We have properties, it's similar to how we inspect in our Firebug or Firefinder. So inspect it, get the property and automate it. So that's all about inspector. So if you have any questions, I'll pocket over for last 10 minutes. And next is need for speed, drive faster than before. So how many of you have automated any web applications here? So how fast it is, how fast it is to execute your automation scripts in web application? Yeah, much slow. What kind of inspect, sorry, locator strategy which we have used? XPath. Yeah, any other locator strategies which you have used? CSS. CSS, bit faster than XPath, but not in IE, at least in IE. Any other inspect locators? Similar to web elements, we have mobile elements and with same XPath, CSS path, ID specific to platforms, which is UI Automator ID or UI Automation ID. So XPaths in mobile is much slower than using XPaths in web. So if we identify any properties using XPaths and automate using XPaths, it's bit slower in your, at least in your browsers, Firefox, whichever browser you use. And when it comes to mobile, it's pretty slower. You can go and have a cup of coffee and come back. And still you will see the automation scripts being still running on. So that's slower. So how to make it faster? So when it comes to mobile, many tool doesn't support CSS and even CSS is very slow in mobile. So we have native elements from Android and iOS, UI Automator IDs and UI Automation IDs. We can use that to make it faster. Is there any other strategies that you use to make your automation scripts faster? I have 2000 or 20,000 functional tests. But I need to go live for every five minutes. How is it possible? Any ideas? Have a very big automation suite which has 20,000 automation scripts that needs to be run in just five minutes or in seconds. Yep. We need to run in parallel. Okay. I can run in parallel. Is it possible to complete those 20,000 scripts in five minutes? How much resource do we use it? We need to have plenty of MacBooks or VMs to run everything in parallel. Headless. One more thing with respect to headless. At least you can't run in headless in iOS. It's a limitation from Apple. And still there is not much tools to run your automation scripts in headless mode. And it's not preferred as well. So for example, if you test your mobile apps in Simulator, it is not the same case in testing the same mobile apps in your real iPhone devices. Any other way? Have you heard of Dockers? Yep. So consume Dockers, scale up and scale down the Docker containers in just minutes, complete everything in seconds. Not even five minutes. Simulators is not like there is no support for Simulators or Mac OS. So Dockers have pretty good support only for Android platform. Like we can scale up plenty of emulators, but still it's a limitation from Docker and Apple site. We can't. For Android we can use Dockers, scale up how many emulators that we need. For example, if you are going to run on Nexus 7 or Google Pixel on 13 emulators at a time, scale up 13 emulators in just few seconds. Opening an emulator in Android, it's a little bit painful. It takes at least a minute to open up. But in Dockers, just in seconds. You can scale up. One is ready. Scale up to how many number of emulators that we need. Any other idea to run your automation scripts in less than minutes of time? The scripts. Drop off of the scripts. Half of them. Yep. How do you drop off of the scripts? The risk analysis. Risk analysis? Nice. There are several organizations which goes live every 11.2 seconds. So they go live every 11.2 seconds. Do we do risk analysis for every 11.2 seconds? No, just to decide which test to keep and which to drop. Yeah. But how does that work? Yeah. So these are the ideas. Run your test faster than before using a parallel strategy. Run your test parallel. Speed up your test on iOS platform, especially on iOS platform. To boot up the simulator, iOS simulator, it takes at least 2-3 minutes. Whereas our entire automation suite needs to be run in less than 2 minutes. So speed up the test on iOS platform by improving the locator finder strategies. Use, not to use expert, rather than use iOS predicates or UI automator, those locator strategies. And next up, spin up multiple servers in less than seconds in one node server instance, which is possible in APM. Dockerize the Android environment to scale up and scale down emulator in seconds. And when it comes to APM or any other tools available in market, open source tools, there are some things that APM does which none of the tools in the open source world does. For example, automating your mobile apps in iOS 10 or 10 plus platforms because it's been very impressive and possible in APM. It supports the moment APM released, sorry, iOS released 10 or 10.1, which is not quite possible in other open source tools available in market. The reason, for example, have automated a mobile app, write on automation scripts for that mobile app, functional scripts for those mobile apps in iOS 9 platform or iOS 9 version or iOS 8 version. It's not possible to execute the same in iOS 10. APM under the hood uses a few libraries provided by Apple and Android. For Android, we have UI automator and for iOS, we had UI automation. Those are the libraries which have been provided by Apple and Google. So APM consumes those libraries to automate your mobile apps, functional scripts in your mobile apps. Whereas UI automation library has been deprecated, completely removed from, completely removed by Apple, I think, one and a half years back. And they have introduced another testing library framework called XE UI test. So we have automated our mobile apps. App behaves the same way in iOS 8 or iOS 9 or iOS 10. But under the hood, automation library provided by those platforms like Apple or Android has a more chance to evolve or more chance to get deprecated decision by Apple or Google. So if we have automated our scripts on iOS 9, for iOS 9, it's not possible to execute on iOS 10 because under the hood, library has been deprecated or removed. So we need to think up to another technology how we can automate apps which are built for iOS 10 or iOS 10.1 or 10.1.1 or 1.2. There are open source tools called Calabash or Android, sorry, APM. APM supports both simulators and real devices. It's possible to execute your automation scripts created in iOS 9. Just change your desired capability. Change the capability and run it in iOS 10. Don't need to change anything else. But other tools don't support your functional scripts written on 9 to execute on iOS 10. So that's the limitation that is why we can say like APM does something more than what other tool does. So that's how it is superior. So you can create n number of server sessions, multiple server sessions from single node instance that we create. APM is a node server and a cross-platform tool. Create a functional script and run it on both Android platform, iOS platform. Same script can run on Firefox, Google Chrome, Internet Explorer, Opera. It's the same way. Create a script, functional script and run it on Android platform, iOS platform and Windows platform. It's a Selenium-like script with few or few changes. For example, we used to call click in Firefox or a browser. We used to call click, whereas when it comes to mobile, we have gestures. How many of you have used 3D touch? Cool. Do you find it difficult to use 3D touch initially? How cool it is? We can land in any page like search from the home screen. So these are the new gestures being introduced in latest iOS platforms. How do we automate those gestures? So Facebook provides a tool called Facebook's WebDriver Inspector which has been adopted by APM. Through APM, we can use the same script, automate any gestures. So construct your own gestures, automate it. In Facebook's WebDriver agent, it is possible, whereas in APM, it's still evolving. So any doubts on how to execute your automation scripts faster than before? Do you have any other ideas apart from dockerizing, running in parallel, anything else? Shall we move on to the next? Have two pretty good goodies. Can we be more interactive? I understand it's Sunday early in the morning. So next is handling multiple simulators at a time. Apple has a limitation to open up or Xcode has a limitation to open up only one simulator at a time. So it's not possible to spin up many simulators in iOS platform that is in a Macbook. So how do we execute our scripts in, for example, in 10 simulators at a time? We need to execute our scripts faster than before. So how do we execute it? But still Apple has a limitation. Can we do it? Okay. So like to execute our automation suit in 20,000 virtual machines, like virtual Mac and spin up a simulator on each and every virtual machine. How costly it is? Yeah, it's very expensive. And it's not possible as well. 20,000 simulators at a time if one got broken in between. So infrastructure is very expensive. And so still we need to execute on multiple simulators at a time. Consider we have a 20,000 automation scripts in our functional suit. How can we execute? Any idea? How do we execute in Android first? And so was on the previous slide. Yep, Docker. So any other idea? How can I spin up at least four emulators at a time? So if you have a Mac book or if you have a Jenny motion installed in your Mac book or Windows PCs can create at least 10 to 12 simulators and still execute, but still it's not enough for 20,000 tests. So existing limitation is, as I said, it's not possible to spin up multiple simulators at a time, but still we need to execute our automation suit and many simulators so that we can have a less execution time. So there are few existing solutions. One is a Project Hydra. It's a Python wrapper to run our automation scripts. We have a Python wrapper on top of multiple simulators. So we can execute our automation suits parallely, but still it internally depends on few Facebook tools, XC tool, and it doesn't have much access to the core simulator APIs to override this limitation from Apple. So that's a limitation from Project Hydra. And next we have a Facebook simulator control. Project Hydra depends on another tool called Facebook's XC tool and it's not been actively maintained by our Facebook engineers, but still they have another tool called Facebook Simulator control. Using this tool we can spin up many simulators at a time and run your automation scripts parallely on all the simulators. Next is Blue Pill, another test runner or the test framework which overrides a course which has a very good control on the core simulator APIs. So they crack down and we can spin up many simulators at a time and run our automation suit. Any other ways to execute our stuff parallely, execute your automation scripts parallely? How do you do in Web? And what kind of tool do we use for automating a Web application? Web browser? Selenium? Selenium, anything? Apart from Selenium? U of T? When it comes to U of T, it has very less browser support or at least the latest versions of Firefox or Chrome. So any doubts here? Before going, I'd like to give away a few steps. Thank you. Can you pass it to him? Your good name? Good name? And next is wearables or TVOS support. So initially we use, for example, we have Web applications to purchase any product. So for that we use Web applications of that, for example if we take Amazon, we have used Amazon.com or Amazon.in to purchase any products online. And next comes, we have a support for wearables. So do we get notifications in our wearables? Where is your product exactly here? And then we use to purchase our products while watching our soccer game and TVs. So we have applications for mobile. So we use to buy the same product in our mobile. Then we get notifications in our wearables. Then even we get notifications on TV when we are online or watching something on our TV. So we have applications for this kind of platform. So are we good to write our automation scripts especially for mobile? A separate automation test for our mobile and separate automation test for our wearables accept the functionality made for, like it may have limited functionality, it just notifies where exactly is your product. So do we write separate test for mobile and separate test for wearable and separate test for TVOS apps? How costly it is? It's very difficult to maintain a regression suit which is separate for mobile, separate for Android, separate for iOS, separate for Android wearables, separate for iOS wearables, separate for TVOS apps. But our objective is to order a product in any platform and get notification on any platform. So we need to identify a tool, automation tool that supports everything like coming from a Selenium like script. It's quite famous Selenium like script. Use it on your mobile, check whether the product reaches a particular destination or particular warehouse and check whether you are getting notification for it in your wearables and check the order status in your TV apps but within the same script. Execute on mobile, execute on wearable, execute on TVOS. How cool it will be to execute a same script on all the platforms that we have. So we'll see. So how many of you have wearables here? Cool. What is the most used app in your wearable? FitNubs app? Cool. Yep. And how do you identify that shows the right time? The importance of testing on TVOS but for wearables I think that it's not so important because most of companies are individuals doing wearable application either for fun or be promoted by Apple or Google. Consider you have application on all three platforms like mobile, wearable, TVOS. You need to ensure that where your product exactly is. You don't have a mobile with you or when you are going for jogging in the morning you need to still find where the product exactly is. Do we get it today or tomorrow? And still you have an application in your wearable app and it notifies you where exactly the product is. Do we test it or just go live every 11.2 seconds? Go live in the user's hotel. That's cool. It's cheaper but you have a reputation for your organization. So you spoil the reputation or you give a better customer support. You spoil the reputation for wearables. Okay. So that you will have a good traffic on your mobile apps. Cool but still it's very important and very evolving. At least you have a fitness app in your wearables. Consider you don't have a fitness app in your mobile. That's specific to wearables. You need to be automated before releasing the product. You walk for one hour and you need to identify how much calories you burnt. Is it possible to get that information? And you don't have an app for TV in TVOS. You don't have an app for the same fitness app in your mobile. So consider you walk for two hours and it says you burnt very less calories for the today. So you will walk for another two hours and ensure that. So that spoils the reputation of the organization. So you need to ensure whether everything works properly. Always we can say it's possible to test the app manually. So every time do you test, consider every 11.2 seconds you have a release. Every time do you test manually, 11.2 seconds is over when you just launch the app. So we will see what is the automation tool that supports all these kind of platforms. So we started with mobile. Then it goes to wearables. Then we are having our snacks in our home and get the notifications on the TVOS in watching our soccer game. And next comes we have advanced platforms like we have HoloLens, Google Glass, any other? We are KIT. So we have wearable, wear apps. Sorry, you have? Samsung Tizen stuff. Anything. So there are libraries to automate our wearable apps. Android wearable apps are easy to test using the existing libraries. But for Apple Watch and TVOS are still a concern. It's not possible. Or we can say Apple as they provide XE UI test for automating their iOS apps. They didn't release any frameworks or libraries to automate their wearable apps. But still they test before releasing the product to you and we consume. We consume their watches, apps, everything. So Facebook has a tool called WebDriver Agent again. It's quite popular and works with TVOS and OSX apps. But still not let officially supported, but still possible. And apart from Apple and iOS, there are a lot of cross-platform applications. Or SDKs provided by many companies. For example, we automate or we create an application in React Native. How many of you have heard about React Native? Cool. We have an application in React Native. Is it possible to automate those kind of applications in existing tools? Consider it can be a Calabash or whatever, or APM. The reason is React Native don't expose many IDs or many properties to identify your mobile elements uniquely. Same way, we have a single code base and launch the app in many platforms like Android and iOS. Single code base cloud platform applications written on React Native can be launched in many platforms like Android, iOS, wearables, whatever. So likewise, we have a cross-platform video apps developed using UI Engine. UI Team provides an SDK to develop a cross-platform application. And that is for mainly TVOS, Android TV. They support Amazon TV. It's an Android platform. We can create a cross-platform application for TVOS, Android TVs using UI Engine. So what they did is they created a node wrapper to automate their applications on top of APM APIs. So when they started automating using a Selenium-like script, we'll see how they automate. And it is a single automation script that runs on TVOS devices, mobile phones, iPads, many devices. So we have an Android phone here, iPad and TVOS, Android TV. So it is the same application developed with a single code base developed for these many devices. We need to ensure that application works perfectly on all three devices. So how cool it is? Single code base, execute on Android phones, iOS phones, TVs, wearables. You don't need to maintain a separate code base for different platforms. So they created a new driver called the APM UI driver and they automate their apps, UI apps. Have you heard about Star Driver Enterprise? How many of you are users of Selenium? Cool. And any version in particular? Let us, yeah, that's very easy to answer. Okay, 2.5, 3.0, yep, anything else? So they have a motto to go near to this Star Driver Enterprise, like automate anything and everything using drivers. So what Selenium did is, initially they used to maintain Firefox drivers. And they got the drivers from Chrome, Safari as an extension, Windows driver. And now they convinced the platform owners like, they convinced Firefox team to maintain the Firefox driver. What is the name of the driver now? Selenium's Firefox driver, yep, it's Gecko. So they convinced their platform owners to maintain their drivers. Similarly, APM was not possible to convince their platform owners. And they both run on same APIs, that is W3Spec, which was created by group of engineers from Facebook, Selenium, Salesforce, APM, Source Labs, many organizations. So the spec is being exposed, automate anything and everything using these specs, follow the specs. And without being locking yourself into a particular driver, create many drivers like, in future it will be watch driver, IOT driver, UMP driver, these drivers are like a wrapper on top of these APIs. And APM will still remain as an interface. Direct this to wearables if you are going to automate in watch driver, direct this to mobile if it is an Android driver. So it's simply a node wrapper. So in future we may have web drivers like with the same Selenium like script, execute your automation scripts on watch, IOT devices, or it can be a VR app or UMP driver. And UMP driver is already live, like same Windows script, Selenium like script, automate on any Windows platform. And next is AI first. So recently on a Google Pixel event, Sundar Pichai has told Google is moving from mobile first to AI first. So use the same APM or Selenium like script. But consider if you have a mobile apps that has AI integrated, how do you feed the data to AI? So can be possible if you have a driver for it. It's not possible to automate entire AI, like it's completely different. So a portion of it feeding the data, get the result and still you can't predict the result, but can be asserted from a group of vocabularies or whatever. So same APM like driver, that's where the future is going to. We started with Android, iOS and Windows apps. Then we migrated to VR apps. Then we got TV OS from Android and iOS. Then we have different devices like VR apps and with VR kits, HoloLens from Microsoft, IOT. So we might have a driver over there, which is an extension of APM or Selenium APIs that consumes with driver spec. Then a portion of it. Any doubts? Any doubts? Yeah. I have a question. Yeah. What do you think is the advantage of using Aptim versus Espresso to make an Android application? Okay. Do you have an application only for Android platform? Only on Android platform? Okay. Both Android and iOS. So are you ready to maintain two scripts, develop in Espresso, develop in Elgrey for iOS? Are you ready to maintain the two scripts parallelly? But you have a same app, which because the functionality remains same on both the apps. It's not the same. Okay. The functionality is very different. It's not very different, but there is different ways to complete the same user flow on Android and iOS. Okay. Okay. Consider we have a different applications, a bit different applications on both Android and iOS, but still are we ready to maintain a single regression suit or different regression suit, one and one written on Espresso, another one on consider Swift 2 using Elgrey, which is from Google. Are you ready to maintain? Down the line. Okay. Cool. Then if you're ready to maintain and if you have enough time to release it, it's up. It's your choice. But if you want to maintain a single script and better choice is APM.