And now, SiliconANGLE TV and Wikibon.org present a focus spotlight. Live from Las Vegas and VMworld 2011, host John Furrier and Dave Vellante, a human being. New models for cloud service providers will support from SolidFire. Hi everybody, we're back. This is Dave Vellante from Wikibon.org and this is SiliconANGLE and SiliconANGLE.tv's continuous coverage of VMworld 2011. I just want to let the audience know out there, if you want to get full coverage of VMworld, go to SiliconANGLE.com, go to SiliconANGLE.tv, go to Wikibon, check it out. You got questions, hopefully we have answers. This is the cloud service provider spotlight segment where profiling, new storage architectures and new enablement, a focus of this spotlight has been quality of service, enabling new applications. And we've got a panel now that we're going to have a discussion around these topics. We just heard SoftLayer and Virtustream, two very interesting disruptive cloud service providers. Duke Skarda is back and Matt Thur from Virtustream, Duke from SoftLayer. We're also joined by David Wright, CEO of SolidFire and also founder of SolidFire as well. So welcome gentlemen. Thank you. Thanks for coming on theCUBE. So David, we heard from Virtustream and SoftLayer. I'd like to start with you. SolidFire, new company, just came out of stealth. We met actually in May at EMC World, ironically. Tell us about SolidFire. Yeah, so SolidFire was really born out of my experience at another cloud service provider at Rackspace. It was there for about a year and a half after they acquired my last company. And I really saw a lot of the challenges that Duke and Matt talked about earlier with providing storage in a cloud environment, providing both the scalable storage that's needed as well as the performance, the quality of service, the availability, everything that's expected of storage in the cloud. And that was really the genesis of SolidFire, the desire to solve some of these challenges with traditional storage. Use really interesting technology like SolidState, compression, deduplication, efficiency technologies to solve both the performance as well as the scalability, cost challenges of primary storage for cloud. So let's get right into it. Maybe share with our audience who might, oftentimes we get the CNBC Wall Street Journal crowd listening in and they might not be as familiar with some of the issues in the areas of storage. So the problem is, if I could set it up and then you guys can correct me or drill in a little further, for years applications have assumed that there's going to be spinning disk out there and spinning disk is slow compared to semiconductor speeds. And now this concept of flash comes in and for the first time we have persistent flash that is much, much faster and it sort of changes the way we think about applications. But there's a drawback. It's expensive. So what we've seen now is tons of innovation in flash, all this money pouring in and we're starting to see prices and configurations come in line with traditional arrays. That changes the way you guys think about architecting storage. So why don't we start right to left with Matt. How does that change the way in which you think about storage? So the advent of the speed and the performance of flash is really, in a lot of ways it's inverted what's been the traditional problem. The traditional problem is we've run out of performance before we've run out of space. And flash technology, in a lot of ways, inverts it. We actually can run out of space before we run out of performance and to my mind that's a far better situation to be in because it's relatively easy to add space. It's never been as easy to add performance. So, Duke, when we think about cloud storage we oftentimes think about object storage or we think about files. Where's block-based storage and applications that run on block-based storage fit in the cloud? Well, it fits in a number of different ways. First of all, black storage is behind a lot of the cloud infrastructures that are out there in a couple of different ways. Either behind a NAS or a SAN. So it's very important from a platform perspective but also as secondary storage. Our customers use it quite a bit as a way to have detached storage that they can move from cloud server to cloud server as well. So, David, when you started SolidFire drawing on your experiences with Rackspace I presume you weren't trying to solve the problem of archiving and backup. What I really saw is that there were a number of smart companies that were focused on the backup and archival piece of cloud storage. Guys like Nervonix and Scality and other guys that were building these large-scale capacity-oriented storage systems. But really there wasn't anybody that was focused on high-performance primary storage. That area, there just was a lot of legacy enterprise hardware and there wasn't much innovation. There wasn't much new stuff coming into that space and even the places where Flash was being introduced it wasn't being done in a way that was really appropriate for the cloud and I really thought that there was a new approach that was needed. There was a different focus on how to use Flash to not just make the system faster because anybody can put Flash in a box and get a lot of performance, but to really focus on the ability to guarantee quality of service, to guarantee SLAs around performance, storage, availability, things like that. Flash could be a component of that solution but there was really a lot more technology that needed to be built around that and that was really what we did with SolidFire. So the good news is a lot of investment going on in this area. There's a lot of competition and that's a good thing in a way because it says you might have a good idea but at the same time there's a lot of competition. So you specifically have taken your company and targeted the cloud service provider marketplace exclusively, right, at least initially. Talk about why. You know I think there are a couple of reasons that we decided to do that. Certainly my background, my experience there, understanding of the market was a big reason to do that but we also felt that it was, as I mentioned, an area that wasn't getting as much attention from either the startups or the big companies. There was a big hole that we needed to fill and there's a lot of other great Flash storage companies, Flash storage startups out there that are targeting other spaces and filling other needs. But this is really the area that we thought was a huge opportunity both now and based on the growth of the cloud it's going to be a huge market in years to come. And virtue stream and software, storage is not your business. You mentioned Dave, you mentioned Nervonix. They're a cloud service provider but they do storage. Storage is not the only thing you guys do and you're selling all types of different services but where's storage fit in the priority pie or the problem pie? Storage has always been from virtualized infrastructures of a few years ago up to the modern cloud service provider storage has always been probably the most difficult problematic area of any infrastructure. And our business is about providing the compute, the horsepower for our customers to run their applications that are enterprise applications and that's not only CPU and memory and network IO, that's disk IO and disk performance and the ability to store the data. So storage is a huge part of it of our design considerations but our business is providing the horsepower. And you would agree with that too? Absolutely. Anything you'd add? Yeah, well I mean there's compute is nothing without either storage and a network to get to it. So our ability to sell compute power and servers is only as good as our ability to sell the rest of the infrastructure their customers need. And as he said storage has always been one of the unsolvable problems. You can only do as much as physics will allow on a spinning disk. SSDs and what a lot of these new guys are doing is they're not just throwing flash at it but they've really stepped back they're taking advantage of the compute power that's available today as well and they're re-architecting the whole way to build an ass which is what's really exciting to us is it's not just putting SSD into a sand they've really reworked the whole way the thing operates. What does that mean for your ability to develop offerings? Do you feel like it cuts your cost of delivering quality of service or is it more than that? Does it allow you to go after a bigger market? I think it's much more than our ability to cut costs. Obviously we always like to be able to to lower our expenses and lower our costs for our customers but this is really much more about being able to enable our customers in a way that we haven't been able to before. So it's really about offering new solutions not just lowering the cost of existing solutions. It's us to complement our quality of service which runs through our infrastructure. It really complements our ability to provide those guarantees and our SLAs of our infrastructure. It just ties very nicely into our ability to do that and it allows us to do it in a very cost-effective manner but it allows us to expand the scope of our services and start looking at new ways to drive innovation and services and really drive value for our customers. So David Wright, I want to ask you, start-up, we know start-ups are faster, more nimble. They focus like a laser on a problem. Hopefully they fly under the radar for a period of time but you're going after some big whales in a way. I mean what you're doing is very disruptive so talk a little bit about the lead that you feel you have. How confident you are in that lead and just add some color there if you could. Yeah, obviously we're very proud of the technology. We're very proud of the architecture that we've built. We think we've got some really unique IP behind that, some really unique architecture that, like I say, is more than just about putting SSD in a box. The challenge that I think a lot of the legacy storage providers have is SSD is so fast it strains every aspect of the storage system. The controller architectures, the processor architectures, the network bottlenecks are very different and you need a different approach to be able to harness all of that power not just to deliver the performance that Flash has but then do interesting things with it. Do things like the data efficiency, the compression, the duplication, the quality of service and we really feel the only way to do that is with a true scale at architecture, an architecture that allows you as you add more capacity to get more CPU, more memory, more network, more processing power to bring to bear to deliver all of that performance and so we really think that's one of the big advantages we have. We're really the first scale at architecture that has been built for them ground up around Flash while certainly Flash can be retrofitted onto existing solutions. You're just not going to be able to get the full benefit that you can derive from it and you're certainly not going to be able to derive the cost efficiencies from technologies like deduplication and compression while still getting that Flash performance unless you've designed your system around that.  So you've got to have the proof points. That's why it's interesting to see SoftLayer and Virtus.Tream. I don't know if the big wheel comes in and says that to you, what's your reaction? Okay, we'll wait. There's risk. There absolutely is risk and we obviously weigh risk versus benefit but 18 months, 9 months in the world of IT and this market that's like dinosaurs to modern man. It moves so fast that you have to take advantage of the technology and if it's the right technology and it pans out and the risk cost benefit is there, you've got to move on it. If I were to put you in a camp, you were in a camp who would take the risk with a startup to get that new value and get the market faster and manage those risks. You've got risk management systems and ways to do that. That's what young companies that are aggressive smart do. Good company. Good, excellent. Thanks very much guys for coming on the Cube and give us a deeper detailed overview of your storage challenges. Dave Wright, good luck with SolidFire and I appreciate you guys coming on. Thank you.


For those of you have been following me for any amount of time You know that I've been on a browser journey of sorts over the last couple years. I've pretty much tried all the browsers out there I've switched back and forth between Firefox and Chrome and un-Google Chromium and Brave and Vivaldi And I mean I've tried them all and I almost always come back to Firefox for many good reasons and to me While Firefox has its problems, that's for sure, and I'm not entirely sure that Mozilla is my favorite company. I Do think that Firefox is overall the absolute best browser on the market now Obviously the market share numbers do not back this up. So this is a personal opinion, but I Really do think that everyone should at least try to use Firefox So what I thought I'd do today is talk about five reasons why everyone should use Firefox Let's go ahead and jump in. So the first reason is Probably the least important reason and that is that it's open source now I know what you're thinking Matt You're an open source advocate and you think that Firefox being open source is the least important reason to use it Yeah, because most people don't care that it's gonna be open source when they use a browser All they care about is does it browse the web and does it do it? Well, that's all they care about if both of those things were false then they would use something different So they honestly aren't going to care that this thing happens to have code that you can fork and make your own or a Code base that you can contribute to whatever that is. They don't most people don't care However, just because that's true doesn't mean that it's not important so when it comes to your ability to trust that your browser is safe secure and Well developed the open nature of Firefox means that you can trust that a little bit more than you can if you use something That is based on proprietary software something like Google Chrome now Google Chrome is technically based on open-source software But Chromium for all intents and purposes must might as well be ran by Google So if you absolutely trust Google then you're not going to have any problems with this But because Firefox is open source there are at least developers out there who can Search through the code base and make sure nothing the farious is going on Whereas that opportunity doesn't even exist when it comes to things like the proprietary parts of Google Chrome being open source also enables Developers to take Firefox and fork it and make other browsers like LibreWolf that offer extra privacy features So that is also a good thing and is only possible because Firefox is open source So moving on to the second one the second one is Customizability so I've talked about this many times on my channel before but Firefox allows you to customize basically everything not only in settings But also the Chrome or the parts of the browser that go around it So you can do something like I've done here where I have the URL bar in the tabs all in one line And I have the my bookmarks here along the side now. This is done through something called user Chrome CSS I've made a couple of videos about that I'll link those in either in the cards or in the video description It's fairly easy, but it's the only browser that lets you do this This customizability is one of the main reasons why I keep coming back to Firefox Despite everything else because I like customizing my browser And this is the only one that allows me to do it to this extent So the customizability of Firefox is actually really good and it's one of the things that makes me most happy to use Firefox The third reason why everyone should try Firefox is the privacy and security now I will not claim that Firefox is the most secure privacy respecting browser out there on the market That is absolutely not true because by default Mozilla actually does collect telemetry So that is something that you need to keep in mind if you're going to use this It can be disabled and because it's open source people can actually look at the cone and make sure it's actually being disabled But it's still something that you need to keep in mind when you use Firefox Outside of that however Firefox does offer a lot more in terms of customizability when it comes to protecting your privacy So it offers different modes that you can use to tweak your performance and privacy settings all the way across the browser or you can go through and Customize each and every little setting so that you can have full control over what is done in Firefox So it also helps to prevent things like trackers things like fishing and stuff like that And while I won't say that Chrome is horrible at this because they do actually have Some privacy features inside Chrome I will say that I trust Mozilla and Firefox to actually turn this stuff off if I turn it off Whereas I'm not sure I actually trust Google to do that because they obviously want my data as much as possible Whereas Mozilla has no interest in collecting your data What's the way we're outside of that telemetry they know they're not gonna sell it to anybody So that is the third reason now number four on the list is going to be something that is very niche and It's only going to apply to a small portion of people But really I've found the extension support in Firefox to be fantastic and there are some things here that are exclusives that you're not going to find on Chrome or chromium-based websites things like Vim Vixen is here I think Vim Vixen is probably the best Vim-based browser plugin that you can find There's another one that I use every day called simple tab groups It's this thing right here and while chromium does have tab groups built in it's not as good as this I don't think so so basically what simple tab groups does is allows you to group your tabs into categories and Then only display certain categories So right now I could be displaying the main group or whatever and that just has those four tabs in it And if I want to switch to a different category, I just click on one of these so like this here I can do that. It's as easy as just changing categories So I love tab groups and I like the way Firefox does them at least through an extension Then the way Chrome does theirs built in The fifth reason is one that is kind of iffy But it's some definitely something that I've noticed and the reason why I say it's iffy is because it's really going to depend on How you use your browser so for me personally Firefox uses less memory than Chrome. It just always has and it still remains true to this day I don't know that that's going to be the same for everyone but I've seen other accounts online where people also say that Firefox uses less RAM and this is important because browsers are notorious for taking up a lot of resources and Usually the resource that is going to be the most precious when it comes to browsing It's going to be the amount of RAM that you have So the fact that Firefox uses less is a good thing Now, like I said, it's going to depend on how you use your browser If you have like a hundred YouTube tabs open Your browser is going to take up a lot of memory no matter what browser you're using So if that's how you use your browser, don't expect to use a very small amount of RAM The one place that Firefox kind of falls down and I'm not sure how this compares to Firefox Or how it compares to Chrome rather Is that it spawns a ton of processes So at one point I think mine was wearing like 200 processes and that which is just nuts It's not even like a process per tab or whatever because I had I did not have that many tabs open But it does seem to spawn a lot of processes and that is a little weird But like I said, I don't know how that compares to Chrome Just to add a couple bonuses on here Firefox is not slow So anybody who tells you well, you should just use Chrome because it's the fastest browser I don't think it's actually true I've never had any problems with Firefox being slow So that is definitely not something that should bother you too much Unless your internet is like super slow or some reason Or perhaps all you use is Google Sites Where they perhaps slow their websites down in other browsers that aren't their own If that's the case, then you should just not use Google services unless you absolutely have to I think that's probably a good rule But you use what you have to to do the job, I suppose So those are the five reasons why I think everyone should try Firefox There are probably other reasons out there that I just didn't think of or didn't fit in the video If you have other reasons why people should use Firefox Or reasons why they shouldn't use Firefox Leave those in the comment section below I'd love to hear from you You can follow me on Twitter at the Linuxcast You can follow me on Mastodon or Odyssey Those links will be in the video description You can support me on Patreon at patreon.com Slash the Linuxcast just like all these fine people Thanks to everybody who does support me on Patreon YouTube You guys are all absolutely amazing people Without you the channel just would not be anywhere close to where it is right now So I thank you so very much for your support Thanks everybody for watching I'll see you next time


Hey guys, how you doing? This is your boy Rich from Rich TV Live and you too can join the club at richpigsdaily.com where you can learn how to win and trade. Hey guys, how you doing? This is your boy Rich from Rich TV Live and Rich Pigs Daily where you can join the club and you can win big if you like to learn how to trade. You came to the right place to Rich Pigs Daily where all we do is find undervalued, underappreciated, underexposed opportunities. First, speaking of that, how about Heli? Put Heli on your watch list, put on your radar. First, Helium with big breaking news announces the 130 light oil discovery at Warsley, significant initial production revenue anticipated in Q1 2022. First, Helium, Inc. Put on your radar, put on your watch list. H-E-L-I on the Toronto Stock Venture Exchange. Two MC in Frankfurt, Germany. A Helium expiration company with access to significant development opportunities across Western Canada. Today announced it has drilled, completed and tested companies first expiration well on the company's Warsley property, the one-thirty. Upon completion, the one-thirty flowed 419 barrels per day of 35 degrees API light oil from the Leduc formation over a test period of 72 hours on a minimal drawdown. First, Helium is preparing to bring the I-thirty into production in early Q1 2022 at a daily production rate of approximately 400 barrels a day. Preparations are underway to put the well into production at a cost of approximately Canadian 500,000 Canadian with first cash flow expected by the end of the first quarter of 2022. Oil production from the well will be transported by truck to select receipt terminals and marketed via third-party marketing agreements. Cash flow from the well will be deployed to accelerate the expiration and development of Helium gas over the company's 79,000 acres of land along the Warsley trend, as well as cover ongoing corporate G&A costs. And based on current price for light oil and an estimated production rate of 400 barrels a day, First Helium estimates the payback of the well to be approximately six months. Management commentary, Ed Beriznicki, President and CEO of First Helium stated, we are extremely pleased with the performance of the I-thirty Discovery well, given current commodity pricing of approximately WTI 65 to 70 USD per barrel and our estimated field netbacks of Canadian 45 to 50 per barrel. Guys, that's pretty good, right? We expect the well to pay out in approximately six months. Mr. Beriznicki added, based on the current implied production trading multiples for Canadian light oil producers, this well represents a significant potential increase in asset value for First Helium shareholders, capturing the aggregate value of this exceptional exploration success along with potential development locations for shareholders will enhance the company's ability to deliver on its key strategic objective of exploring for and developing Helium production in the Warsley trend. David Safton, Vice President, Geoscience commented, while this drilling result confirms our geologic model over the prolific Warsley trend and bolsters our confidence in our exploration strategy for the region, it also demonstrates that given the location of the Warsley trend within the Western Canadian sedimentary basin, the WCSB, there is also a real probability of discovering reasonably large economic pools of light oil, which I believe will be hugely, hugely rewarding. Mr. Safton added, the flow test results indicate a significant commercial accumulation of high quality oil, while Leduc oil accumulations along the Warsley trend are not as common as our primary target, Leduc gas, we estimate that approximately 20% of Leduc wells present as oil wells. Drilling and logging information from the borehole indicate that two additional formulations are prospective for Helium. One-30 highlights drilled based on a detailed 3D seismic evaluation. The one-30 confirms the company's geologic model over the area based on the company's assessment of the economic Leduc wells along the Warsley trend, approximately 20% have been light oil producers. The balance has been natural gas producers. Key features of the one-30 include production tested at 419 barrels per day of 35-degree API light oil, flowed over a period of 72 hours with minimal drawdown at a total drill and complete cost of approximately 1.9 million Canadian production test results for the one-30 suggest that it is an exceptional vertical oil well in the WCSB. The one-30 will provide the company with flexibility in securing funding to continue with its primary strategic objective, which is to explore and develop its land holdings on the Helium-rich Warsley trend. And once production on the one-30 is established, the company intends to engage its independent reserve engineering consultant to evaluate the one-30 well for inclusion in year-end corporate contingent resource and reserve estimates in accordance with 51-101 guidelines. This would include an independent estimate of the net present value of the reserves associated with the one-30. What are the next steps based on the further evaluation of these expiration results? First Helium will be confirming its drilling program at Warsley for H1 2022, which will include prioritizing its drill prospect inventory for Helium, favoring locations which may also provide exposure to the potential for light oil accumulations, selecting its next Helium drill location and commencing drilling in early 2022, evaluating a number of lower-cost well bore re-entries on the existing Warsley land base and on lands acquired during the recently announced land and infrastructure acquisitions and evaluating potential light oil development locations on the one-30 pool in connection with exploring alternatives to monetize one-30's asset value. Over the first half of 2022, the company will evaluate alternatives for monetizing the intrinsic asset value of one-30 to further its strategic Helium exploration and development objectives. This may include entering into hedging arrangements to guarantee predictable levels of cash flow for ongoing project development and possible underpinning of gas processing, facility financing alternatives. So let's tell you a little bit about First Helium. Once again, the symbol is Heli H-E-L-I. First Helium Inc. is a Helium exploration and development company operating in the Warsley area of Alberta, Canada in response to the shifting supply dynamics of global Helium marketplace. First Helium was founded to capitalize on the untapped potential of significant Helium resources in Western Canada, building on its successful discovery well, which has repeatedly, which has had repeated production tested at over 1.3% of Helium content and 65% natural gas content and its one-30 success. First Helium is working to develop its land base of over 79,000 acres along the highly prospective Warsley Helium trend and 276,000 acres of select exploration option lands located in Southeast Alberta, nearing existing Helium operations to establish its operating base. First Helium seeks to market its Helium gas into North American market via term off take marketing agreements and arrangements with established third party distribution companies. So let's just break this down. This is huge, huge, huge news for First Helium. So to break this down, the netback in the release is their margin per barrel, which is $45 to $50 Canadian. So to calculate how much revenue First Helium will be having per month, you have to do the following. 400 barrels a day times $45 a barrel will take on the low end, we're gonna be conservative, times 30 days equals 540,000 Canadian per month, which they anticipate this revenue should flow for approximately a minimum of six months. So that's 540,000 Canadian per month for a minimum of six months. So approximately 3 million Canadian over the next six months for First Helium. Pretty huge. And they will also be continuing to explore for Helium targets where there could be oil backup. And I just wanna make sure everybody understands that First Helium is an expiration company and not an oil and gas company, okay? Despite the fact that they have found and struck some oil, they're not an oil and gas company. The uses of Helium gas and liquid Helium by industry, just so you guys are understood and aware, what are the industries that are using Helium? Aerospace and aircraft from manufacturing to flight, Helium is widely utilized throughout the aerospace and aircraft industry, automotive and transportation equipment, diving, electronics, healthcare, welding and metal fabrication, just to name a few areas of focus and interest for First Helium. Now let's just break down some more information on First Helium. All right, so you guys can see here, this is their website, firsthelium.com. Please go to the website, learn more about the company. You can learn more about First Helium, learn about them, get investor information and even contact them. You can see a project-driven Helium discovery development and production company. And if we scroll down, you can see here, First Helium Inc. is a Canadian company developing Helium production to meet growing demand in the high-tech global market. Companies position to become a leading North American producer, leveraging a de-risk strategy to achieve near-term cash flow. The company has recently raised approximately 12 million, which it will develop and deploy primarily to the development of its Warsley Helium project, anchored by its successful Helium discovery well. And you can see here, First Helium is well positioned to deliver Helium production and cash flow growth from its Warsley property, which will drive future expansion from its extensive portfolio of exploration lands and prospective territory. And it is a critical finite resource. Helium is a relatively uncommon on earth, despite being the second most prevalent element in the universe, Helium is very difficult to trap and store due to its lack of density. It quickly rises and dissipates into the atmosphere. The majority of atmosphere, Helium is lost as it escapes the atmosphere and into space. Canada's well positioned to be the next major North American producer of Helium. And I believe if you're looking for a Helium stock, put First Helium on your radar, put it on your watch list, HELLY H-E-L-I. Big technology companies like Amazon, Google, Facebook and Netflix all depend on this gas to keep their servers running around the flock. Helium has everyday applications in the technology and medical industries as well as space travel and national security among others. You can see here, it's a critical gas for building cars, high speed internet cables, phones, tablets and computers required in the health sector to cool magnets in MRI machines, identified as one of the 35 minerals crucial to the US national security. Now let's take a look at the stock price. So what I've done is I've marked the zone which I would consider the buy zone. You can see here, it's been public since August when it hit its high high and I'll mark its high high. All right, we'll mark the high high of the zone which was about 38 and a half cents. And you can see the low, low of the zone which is about 18 cents and we're currently sitting at 21 and a half. So in my opinion, based on the charts, based on the fact that they've got some really big revenues coming and we've got some growth, they've raised some money and I feel like this is a company that is very undervalued, extremely underappreciated and underexposed. I believe that we are already in the buy zone and I feel like based on the chart and you can see it on the chart yourself, these zones of 21 and a half and lower would be what I would consider the buy zone. So if you can get into these levels or lower, I think you're doing pretty good and then I think the upside all the way from these levels, let's just say you got into 21 and a half or say you got into 21 and a half right around here and then you brought it up and it went back to its all-time highs of 38 cents. The upside to all-time highs from these levels is around 80%. So big upside for Helly to go back to its all-time highs, which it did right around its IPO date. So it's never gone back there and I believe that there's a very good chance with these wells now getting into production and the revenue potential of 540,000 per month Canadian for the next six months that we could see them go back to those levels and beyond which would be a nice return for investors at these levels. Now I wanted to also show you a little bit about their investor's deck. You could see here first Healing is well positioned to deliver healing production and cash flow from its Warsley project, which will drive future expansion from its substantial inventory of expiration projects that is directly from the CEO who hopefully I'll be able to interview and get on our show pretty soon. You can see company overview and highlights. Company has a strong working capital position of 7.5 million which it is deploying primarily to the development of its Warsley helium project anchored by successful Discovery Well. The Discovery Well has tested at 1.3% helium content and 65% natural gas content. First, helium has a land and seismic review and given its advanced helium acid base the company's common shares trade at a compelling valuation. So what are the investment highlights? Global demand, helium is a high value finite resource vital to the aerospace healthcare and high tech sectors because of its physical properties compelling economics, long life, high netback production profile lends itself to responsible non-diluted financing alternatives for infrastructure large undeveloped land base over 79,000 acres of prospective helium bearing lands on trend with the Discovery Well large expiration inventory potential expensive seismic and land review option on over 880,000 acres of prospective helium expiration land resource de-risk the company's helium rich discovery Well is ready to be equipped and brought into production attractive valuation with the production ready Discovery Well qualified by an independent engineering evaluation and contiguous upside lands first helium is attractively valued relative to its public company peers liquidity first helium's common shares were listed on the TSXV on July 12th ticker Helly so only been public for a few months and environmentally conscious first helium is committed to leading the way in environmental and operational excellence in the nascent Canadian helium expiration and development sector striving to surpass government regulations now I'm gonna tell you guys something we talked to a lot of companies very few of them are helium companies so if you're looking for a helium stock you need to put this on your radar and put on your watch list right now you can see some of the comparisons to the peer group comparison highlights Healy stands up from its peers with a production test to Discovery Well backed by independent engineering evaluation report so you can see here some of the other companies that have much larger market caps and you can see their land positions and right now independent engineering evaluation, contingent resource estimate the only one is first helium that means bingo to me folks and performance tests you can once again see that first helium is one of the only ones that actually has three extended flow tests most recent a 10 day test so huge, huge, huge opportunity right now and a baby market cap for first helium and you can see some of their peers imperial helium, IHC, global helium, HECO blue star helium, BNL, royal helium, RHC and eventi energy, AVN and desert mountain DME all with bigger market caps with first helium so not many companies out there to compare themselves to but when you do compare themselves to the handful of companies that do exist they look undervalued I mean look at the baby market cap despite the fact that they have a nice land position they've got independent engineering evaluation which nobody else has and performance tests so in my opinion they are well positioned to explode you can look at the corporate bench depth so this is their management team look at their experience first helium boasts a season management team board and advisor group with successful track record and experience in oil and gas exploration and production capital markets and finance helium project development construction and project management and mining exploration and development you can see Vance Lober who is the founder Ed Beriznicki who is the present CEO and director Robert J. Scott who's the CFO and director David Safton who's the vice president of geosciences and Sean Weizikowski the vice president of engineering and you can see all of their experience so very experienced management team you can see the capitalization and ownership management and directors collectively own or control 20% of the company's outstanding common shares so they got skin in the game share capitalization table basic shares 65.6 million options of 6.1 million warrants 28.4 million fully diluted 100 million shares and you guys know I love companies with 100 million shares or less this is 100 million shares fully diluted with approximately 7.5 million in cash management directors advisors and key shareholders collectively own or control 38% of the company's outstanding common shares so it's extremely tightly held what are the next steps for the next 18 months warsley project activities perform detailed warsley facility engineering and design secure facility financing strategy and order equipment begin to drill and production tests new warsley wells commission facility and commence healing production exploration upside this activities finalize technical evaluation of warsley undeveloped lands continue seismic data interpretation on new areas of lands and prioritize and position for further exploration drilling at warsley and new area lands a very attractive valuation first helium compares well to its trading group peers we broke that down already only a 12.8 million market cap a baby market cap with 7.5 million cash in hand and more revenue coming all right so that's what we got for first helium ink love to know what you guys think about this video if you like this video smash the like button comment down below share the video everywhere and subscribe you can learn more at their website at first helium.com where you can go and learn more about this company now I must remind you that rick tv live is strictly for information and education purposes please do your due diligence do your research before you invest in anything we talk about or discuss here on rick tv live in saying that we believe that this is a company that is grossly undervalued underappreciated under exposed put on your radar put on your watch list huge big news what do you guys think comment on the video let me know what do you think about helly H-E-L-I first helium first helium ink I think has a chance to be a huge winner to put on your radar put on your watch list and let me know what you guys think do you already own this stock are you thinking about buying this stock is it at the right price are you waiting for a dip let me know is your boy rich from rick tv live I think it has a chance to be a special deal we don't hear about too many helium companies I'm gonna start researching more and more about helium companies but I think this is a small cap helium company with money in the bank and a baby market cap with room to grow left to know what you guys think comment on the video let me know what you think about first helium ink is your boy rich from rick tv live bringing you a helly H-E-L-I first helium ink what do you guys think is your boy rich from rick tv live and I'm out


so welcome to the next session of embedded software testing unit 4 so this will be the last lecture session of unit 4 on the software integration and we have a regression testing we will study about the software integration the considerations and other aspects the environments and followed by that we will discuss and study about the regression testing okay to recap on software integration we know that the integration can be done at system level software level and the hardware so it is called system integration test software software integration test hardware software integration test so to recap the integration test strategy is not just enough to have a component level testing but to have a adherence at the system level how the components interact at a module level when they are logically grouped we need to work out a strategy to integrate those components so there are different analogies like in terms of strategies as and when they are developed we can do or we can start with the top level modules will be lowest possible units so either way we use the steps and drivers test drivers it is called basically to make sure that the different stages of their development integration can be taken up so different strategies we had a comparison in terms of over time and the needness of the component drivers for the steps parallelism ability to test the particular parts ability to plan and control the sequences also we had gone through the advantages of top down and the bottom up so top down has advantages in terms of if major defects are more likely to top level modules then this is better whereas in bottom up at the lowest level possible device drivers or hardware dependent things are having issues better to do the bottom up testing so basically a look and feel of the system in terms of demonstrating what could be the architecture or what could be underneath the embedded systems can be well demonstrated in top down testing because we have more testing from the top post modules whereas in the bottom up testing we start with the lowest possible modules and when they are completed with the help of drivers because driver needs to call them so that is where we use the bottom up test strategy but we need to have that is why this is disadvantage because we do not know what also we need to use for creating a driver or we need to have our own drivers so that is why the disadvantage of bottom up whereas in top down testing we need to develop the stubs so there are a lot of small stubs that may be required so that is a disadvantage it may not be accurate there could be some errors while developing the stubs itself so it takes significant amount of effort and time in terms of developing the stubs so that is what we are going to do top down testing the other type of test called hybrid test which uses both top down as well as bottom up so this has been preferred in many of the industry aspects where larger systems are there and where a lot of subsystems are there having a small to moderate or moderate to complex high complex embedded systems or embedded subsystem so it is beneficial to have a hybrid test strategy which has a combination of both test stubs and test drivers that means it is like a middle out approach I mean both top down as well as bottom up sort of a mechanism so this approach basically factor based on the criticality and the cost that the system has so it is very subjective so based on that we can take a call in terms of using hybrid test strategy where to apply where to use what sort of a testing mechanism in terms of integration so another type of integration testing we had gone through is called centralized integration this is more appropriate here use kernel or OS because we cannot replace those part of the embedded system so surrounding that we are going to develop anything that is required so we cannot substitute or very difficult to substitute the stub so this kind of a approach is called centralized integration so surrounding the centralized part of the system is developed first and made ready for production there are other type of integration we have gone through quickly layer integration where different layer for you application layer lower layer and the device drivers of the hardware layer this is particularly useful which I think what you tell is that when we test a protocol such as a network protocol so better to have layered side of a testing so we know that OSI ISO model has transport network data layer physical layer these are the important elements of course we have application presentation and session layers top most of that this is presentation layer application layer as a top most then we have a transport network data and physical so likewise we can segregate it so something like a layered so we have a seven layer approach where protocols of networking applications use this OSI model used for network systems where protocol network protocol TCP AP FTP IP UP IP UDP all this sort of a protocol mechanisms we have a layered approach so in this case better to use a layer type of integration where we develop the integration test in terms of the other type of integration testing is client server integration we had studied about this where the server is stubbed when client is tested client is stubbed when server is being tested so it is like a collaborative mechanism in terms of client and server this is typically used where we have a database and huge application database oriented object based or object oriented systems we have my last type is a collaboration where we identify different collaboration models those models can be integrated together that is where collaboration integration can be done so those are the different types of integration that we have studied then we came to integration test environment how it looks like so basically it should have a mix of both unit level testing environment as well as system testing environment because we need to develop a driver with the help of integrated development environment that environment could be used for developing the system ambulance testing the system level identification similarly we use the lowest possible device drivers test drivers so those features also are needed so both sort of a environment is required for doing the integration testing so it is like an integration model which will comprise of which will be comprising of both unit level as well as system level environment basically we can use some of the test driver model which have been working and which are useful for integration to logically test the different models together additionally we may need tools like monitors to log and read the data traffic as I said in the protocol there will be a logger time stamp and all that to do that we need to have an appropriate additional tools such as monitors so in continuation of integration test environment so we know that software unit test and the software integration test test bed is created basically which is comparable to the test environment for the simulation model so we know that simulation simulation and actual hardware or target based testing are used so accordingly we are going to have a test environment so that is where we develop the integration test environment so basically prototype stage and production stage are different type of integration we can have so both the cases we need a test object having the executable version of the software unit or integrated software units need to be used so that is basically developed based basis of the design or generated from the simulation model so based on that those integration environment will develop so in continuation of this host based environment target based environment then host target a mix of that can be used as well in terms of developing the integration test environment also we had gone through a table from the book in terms of levels of simulation how it can be done and where it can be used what is the processor used host processor is enough for doing the experimental or host based integration testing whereas when we use the emulator we need to have a target actually the real target having the target processor used so actual hardware enters of memory or any transceivers or any communication devices we need to have a mechanism such as hardware in loop or hardware software in loop sort of a test environment for integration test specifically it is useful for hardware software integration not the software software integration software integration we can have the host based test environment for the target based environment we need to have hardware software target environment for doing the integration test so that is about the earlier session today we will study more on further integration test environment the below table is a depiction of a simulation level for hardware software integration test we can have sort of a simulation in hardware software integration where this table you can see the embedded software very different it can be on the experimental host some of the pieces of the embedded software can be experimented or run on the host so that is where the first test bed is going to be lying the next one could be on the real hardware which uses some of the software units software integrated in it in the first one also the software units will be used there is no hardware involved the last one being hardware software integration the complete environment and system environment having the embedded software so the various process that are being used for this three layers of simulation in the hardware software integration or see the first one we need a host based process such as x86 or 386 46 or code 2 i3 Intel based or AMD based etc the OS can be Windows Linux whatever it could be but the host the execution will be based on the processor host based processor and in this case the rest of the embedded systems will be formulated a plant you do not need to concentrate much because plant is something like where we are going to have it what is the unit called actually the second one will have a emulator because we are using the real target and we need to simulate the system itself completely with the help of this emulator and the last one we have the real target and the processor is real target there is no emulation of the target processor that is how we are going to have the layers of simulation level in terms of integration testing so this table provides an overview of the level of simulation of the hardware integration test the columns refer to the simulation area of the generic scheme of an embedded system so continuation of integration test there is a system integration test which is at very higher level of the integration test on top of hardware software or software software integration test so what we do here the test and armament for developing the system integration test is a test armament test and armament is very similar to that of the hardware software integration test after all the complete embedded system is also a piece of hardware software so it is not something different but it is as a whole the hardware software and the integrated models combined together something like a system test it is also can be called a system test but the emphasis or focus is on the integration of the various logical model of the embedded system or the embedded software one difference may be found in the fact that the prototype printed circuit board of the complete system is provided with its final input output and the power supply connectors the offering of stimuli and the monitoring of output signals possibly combined with the dynamic simulation will take place via these connectors so actually in the display something like a actual target board we are going to use and prototype of printed circuit board of the complete system will be provided as a pre-production testing where we use a actual input output and power supply connectors and we use the system integration test strategy for doing this developed board basically the pre-production board it is called a system integration test board what it will have basically is that I will try to draw one as a production as a pre-production we can call this as a pre-production board so what is the difference between this so what will happen is if there are going to be any bugs or any fixes are needed all those final stages of the work will be done on the pre-production board and to test that definitely we need a interfaces right like we need a debugger we need any of the test hooks in terms of ports all this intermediate stuff will be part of this pre-production board which is slightly a larger bone or actually larger than the actual production board both will have the same processor basically in both the cases what will happen is the additional circuitry that is required will be taken out so in this case what will happen is pre-production minus additional circuit will be removed in the production board so that it can be used purely for the deployment on to the target system or the field actually which will be delivered to the customer so that it will not revert back to the factory so this is the final production board so all the system test acceptance test all that will be done on the production board whereas in the integration stage we are going to use the pre-production board so that is where the difference is like the next one is another table you can see for system integration test this table basically depicts simulation level for system integration test you can see the last one being added here as a real target with the system integration and rest of the systems or prototype and actual plant is simulated so this table provides an overview of the level of simulation in the system integration test the columns refer to the simulation areas in the generic scheme of the embedded systems so in the earlier one we didn't have the system integration facility in terms of the actual target and there is no experimental system actual systems will be there so that is what we going to be prototyped so this will be used for system integration test something like a pre-production testing this is called as okay so let's move on to the next topic of the integration test so this is basically the use case derived or use case integration test so what we do here is you may be knowing about use cases basically this term is a derived term from the UML I think I will have an explanation about that UML perspective because we are not going to discuss much on the UML why because UML has its own deep study required but basically let's understand that unified modeling language which uses use cases class diagrams sequence diagrams etc so basically it is going to depict how the system looks like so something like a model we are going to have so from the user's perspective the cases that are going to be developed or the classes that are going to be developed are called use cases so definitely we know that use cases are being developed we have an input we what is the expected output all that are described in use cases so with the help of use cases we can develop the test cases and that use cases concept only on the higher level modules or the graphical group or the functionality or the features of the embedded software system so that is how we can derive the test cases from this use cases that is where it is called as integration from use cases perspective basically testing from use case which are further going to be broken down into test cases so basic difference is that use cases tell the story of how someone interacts with a software system or the observed behaviors that's what use case the user perspective does to achieve a goal could be accepting some value and computing something and resulting some other value or achieving some of the results that could be a functional block for that goal a good use case will describe the interactions that lead to either achieving or abandon abandoning the goal so basically the use case describes the interactions for achieving the goal or resulting the path whatever that goal is going to take for that functionality the use case will describe multiple paths that the user can follow within the use case so use cases can have different paths we know that as the flow of the program control level or data level goes and it subject to the complexity and the flow what that embedded system arrives similarly multiple path that use case can perceive so we will also can be used to draw the test cases so it is test case represent one set of inputs that exercise a single use case scenario that means use cases will have multiple scenarios so one test case for each scenario we are going to have so that is where test cases have been derived from the use cases let us see try to see more examples on this integration from use cases perspective integration from use case perspective system test cases how are going to write it many system many system tests are designed to simulate how a user interacts with the system to make sure that the system responds appropriately because system needs to be subjected to some sort of interaction and the response if we have defined your requirement by using goal driven use case that means we are going to achieve some goal with so many paths you can use the use cases as a framework for defining this test cases definitely this use cases are important and useful why because this framework on top of which we can draw a lot of test cases and there is a goal for this framework the framework is basically the use cases also called as goal driven use cases so how are we what are we going to come up with with the help of this goal driven use cases nothing but the system test cases the system tests should be created to test a single situation that means each test will try to test the individual scenario or the situation when using the approach of use cases and use case scenario to describe requirements a system test should test single use case scenario so what it is trying to say is each use case or every single use case scenario should have a test case in that way we are going to have system test cases covered addressing to the requirements so that is where the requirements are going to be tested from the use case perspective so the next one is how we are going to generate generating test cases from use cases use cases are based on the unified modeling language as I said UML is used and can be visually represented in use case diagrams I will not detail out the use case diagrams maybe an example I will try to see when we are going to have a practical class of a sample UML so use case diagrams basically will have users interacting with the system suppose I will try to draw a small listing so this is the functional block and we have a user user will be represented in a different way so basically this is a use case so what it does is it tries to interact with the system and it expects some output from the system so all these scenarios like we have one or two and some results like two and three and four whatever it could be other functional block all this help of use case diagram we can draw test cases test cases can cover from this this this this this likewise so that is how we are going to generate test cases for each of this part where use cases are being used with a user interfaces with the system and the expected output how the user pursues from that scenario and the use cases will have the below items you can see name and description of that use case flow of events that use case can take or different flow of that events how it is going to drive and any special requirements is going to cover because having the user perspective we may cover more functionality or more requirements or any specific requirements or special requirements that are also addressed when any preconditions that needs to be taken care for typically executing that use case and any post conditions in terms of the test cases have been executed we need to take care so all these aspects of use case to test case will have to be taken care so that is where we use the test cases generated from use cases basically whatever I try to draw that users it is also called as actors actors are nothing but the users which the users can be any subsystems or any humans or actual users so the lines whatever I try to draw communication between the actor and the use case in terms of the flow basically so use case diagrams will provide the bigger picture in terms of how the functional block is getting used or perceived and the same thing will be tested against that actually the next one is an example of generating a test case you can see a different parts in this use case flow basically so this diagram depicts a basic law of events and alternate flows of events per a use case so what is going to happen is the basic flow will be same the user going to use that functional block there is a output but to achieve that there could be a different flows alternate flow 1 2 3 4 different color sequences have been followed and these alternate flows can be derived into sub alternate flows as well so in this way in that way we can have the multiple flows as well so this multiple flows will have each one address by a different test cases is called flow of events and for each of each flow of events there is a test case and we need to apply all these items all these descriptive things all these pointers for addressing the use cases you can see there are different scenarios and scenario 1 could be a basic flow scenario 2 could be the alternate flow and scenario 3 could be alternate flow 1 alternate flow 2 scenario 4 could be alternate flow 1 2 3 you can see multiple scenarios so it can take this path basic flow alternate 1 2 and alternate 1 2 then alternate 3 it goes back and again it comes all 4 can be there likewise we can have multiple scenarios for each scenario 1 test case we are going to have it so once we identify these flows for in this example 5 flows are there we are going to generate the test cases so how we are going to generate the test cases is set of test inputs execution condition writing type use cases act as a product requirements for generate the test case this is this is where it is very important to understand that we have understood the requirements and we have written the grouped scenarios based on the use cases now it is a time for us to write the test cases and for test case writing we will not care about requirements and all on a major aspect but we care about the use cases so you can use cases become something like a product requirement those product requirements will have to be addressed for developing the test cases and executing them so this is what is the important thing so it involves basically three steps process for each use case generate a full set of use case scenarios for each scenario identify at least one test case and the conditions that will make it execute it can be more than one test case also subject to the feasibility of that particular use case if it requires a derived test case or more test cases nothing wrong in having more than one test case it should be executable those test cases that is where they are going to have a theoretical as well as practical procedures for these scenarios for each test case identify the data values with which it has to be tested so step one is to generate the scenario step two to two is to identify the test cases step three is identify the data values which is very important so once again I will repeat read the use case of textual description and identify each combination of main and alternate flows as you can see different scenarios you have to identify that and understand the scenarios and create the scenario matrix you can draw a table and identify the matrix it could be a partial matrix or full matrix for a partial scenario whatever it could be but the end goal is to make sure that all the use case scenarios are addressed with the test cases that is how we are going to draw the scenarios that is the first step second step once the full step of full set of scenarios have been identified the next step is identifying the test cases we can do this by analyzing the scenarios and reviewing the use case textual description as well so use cases will have a description as I said in one of the earlier section earlier this slide each use case will have a description and this description is being used as a textual input for developing the analyzing the scenario and taking the use cases or test cases from the use case so there should be at least one test case for each model but there will probably by more actually depends subjectively so the additional test cases are basically to cover all the possibilities in terms of boundary equivalence whatever we want to call it whatever we have studied earlier for dynamic testing in addition we may wish to add test cases in terms of analysis or anything that could make it cover for all the scenarios so that needs to be tabled out that is where what we do with the test cases identification process the third step will be identifying the data values for each of these tests because data values are very important once all of these test cases have been identified they should be reviewed basically understand and validate to ensure accuracy and to identify redundant or missing test cases anything is missing we need to do it then so once they are all understood reviewed approved the final step is to actually we have to substitute the practical values or the data values for the inputs and the expected outputs so without a test data test cases can't be implemented or executed right so they are just descriptions of condition scenarios and paths but actually the test data is going to identify the practicality of the testing so therefore it is necessary to identify actual values to be used in the final test so this also can be done with help of a test case matrix for each of the scenario okay so with this the generating test cases from use cases comes to an end so next topic in the integration or continuation of the integration testing is the continual integration testing or this called incremental testing or it is also called as mainly regression testing regression testing so what do you mean by regression testing it means re-learning test cases from existing test source to build confidence that software changes have no unintended side effects so why we need to have software changes why because when we have done that primary testing or first-time testing there are certain issues and bugs we found out on the embedded system of the software to overcome that we are fixed that software and the requirements are not changed test cases should not change so what has to change is the result and to achieve that we are going to have regression testing so regression testing means re-learning the test cases from the existing the test suits test suit is a set of test case test procedure on the test execution scripts on the test bed so basically while doing this we get a confidence that the software has got some changes but does not have any unintended side effects the ideal process would be to create an extensive test suit and run it after each and every change that means the test suit should be such a way that any changes in the system will not alter the execution process so we do not have to retouch or rework on that test suit again and again though the system is under the changes so changes means changes within the certain limit or the scope of the program that is where the regression testing is held out is a important type of testing it is not a type I would say it is a process which everybody will follow in the all the industries but some people do a automation for regression they have a dedicated team for regression they do batch automation script automation execution so that every version of the software they keep testing it independently that is where the regression testing is very important but whatever that you want to have it in regression testing the primary testing has to be solid on the accurate and clear so that the regression testing will be successful based on that so definition of a retesting based on standard 79251 it says that running a test more than once that means same test is getting repeated a simple definition so under definition is a retesting to a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made so we call it as retesting and regression testing retesting is just testing again regression testing is previously it has been tested some modifications have been done or the faults that was identified and we are going to re-execute or retest the same thing so that we are going to fix and those faults have been uncovered or changes have been fixed let us see in detail regression testing why it is important and different definitions and techniques that are used for regression testing maintenance testing would have heard it is same as regression testing what are the things that we are going to have for maintenance testing basically this is the one it is also called as one of the strategy for maintenance testing there are other aspects also in maintenance testing but the main aspect is that regression testing or retesting is done intended changes of system behavior must be tested but it is also possible that the system which used to work correctly in the previous release does not work in the new release as a side effect of the implemented changes this is called as regression so we know that incrementally there is some issue that it was working before but it is not working so what is the reason why because we found out the issue in X place and that issue is fixed so X place is working fine but while doing the testing of the X we also test why is it working fine and no changes on that but it is failing now so there is a side effect so all this will be brought out that is called as regression regression testing much of the test effort is dedicated to testing that previously it was currently first currently so basically what it is we make sure that the earlier working testing is being again probably so that is where the effort goes of course we know the fixes that we have done for the identified faults or errors in that we will work that is working but the emphasis the regression is that it is going to be changed against what was looking earlier again it should work the same way so the changes can in turn be itself not into a limited test focused only on the change alone or a complete test of the test of the function or component that has been changed a test of the coherence and interaction of the change component with adjacent form so the three types of changes that it is testing can take place that is on the direct point where a limited test focused only on the change alone means only the change you are going to that will see that in build we verify so it is going to be working but that may not be enough because the changes can be impacting the surrounding models so the second type of changes can be a complete test of the function entire function function has some small functions or substance pumps but that is not enough that does not mean that is enough to test only that interactive part or the interactive body of the function or the component but it is better to test the entire component that is what it means the second build the third one is why we do the testing of that particular component we need to check the coherence and interaction of other components and the other model which is having the interaction with the current one which is under test so that is where the regression testing is very much important so with every implementation of the change we know that the risk of regression is introduced regression testing is a standard element in the maintenance test project visually a specific set of test cases is maintained for this purpose generally they do a sample on the maintenance depending on the risks and the test budget available a choice has to be made to either execute the full regression test set or to make a selection of the most relevant test cases test tools can also be used effectively to support the execution of the regression test when the regression test is largely applicable selecting which regression test cases to skip is no longer necessary because the full regression test can be executed with limited effort basically that is why we do not need to skip so regression testing test strategy so what are test strategies that we can have it is basically depending on the number of changes so definitely regression testing can be carried out subject to how much changes there and what is the kind of change that is also important it is not that number of changes 10 numbers 20 numbers present matter even one change can also lead to a huge risk or regression so that is very important changes as basis for risk evaluation planning and progress tracking so the changes that have been there on the embedded software due to earlier fixes has to be evaluated planning and progress tracking also need to be taken care for the regression testing so it can be treated in the same way as your newly developed that means some of the functionality needs to be addressed for the regression testing such a way that functionality is being newly developed and we are going to test it first so the test strategy could be determining the changes the first part is implemented change request and corrected defects so what is been implemented what is been changed that we need to determine first second is determining the relative importance of the changes and regression that means we need to identify importance of the changes on the regression importance third one being selecting quality characteristics what are the quality aspects that we need to take care in terms of the checklist or this criteria all this have to be taken care fourth one being determining the relative importance of the quality characteristics is not just enough to identify or select the quality characteristics for that particular scenario it is also important to understand the relatedness of the quality aspects the next one is determining the relative importance per change and regression or quality so each changes what is the relative importance of the entire system to that particular change or the particular quality characteristics all this above steps need to be combined together to come to a conclusion that is called characteristics combination the sixth one being establishing the test techniques to be used this will become six okay so then we are going to establish the test technique for that identified changes that is what the steps that are involved for regression testing so what are the areas that regression testing of the taken care regression is due to fixing the fault side effects we need to check you know that we have found a field problem in terms of fault or error and that is fixed and we are going to do a regression test on the fixed part so we need to check the side effects of the fixed part also okay regression due to added new functionality so new version of the software has come so that doesn't mean that we need to have entire testing developed from the scratch so one into what we need to do is regression or incremental testing in terms of that particular added functionality or the new functionality regression due to a new platform that means the same software same testing will be carried out on a new platform this is very specifically important where we do a voting activity so especially OAS related things also operating systems are supposed to work same on different platforms it could be Intel it could be AMD or any other sort of a platform Linux you take for example Linux OS is supposed to work on different hardware platforms so how they are going to do is to with the regression test strategy regression can be due to new configuration or after the customization some changes some configuration there is no software change still but the environment or the configuration of the program or the software under test has changed and regression is required for the same regression and delivery planning so those are that is also one of the area that need to be taken care for regression testing so how we are going to deliver so as a what incremental on incremental all this will be part of the regression testing areas so the next part is regression testing automation so very important to have automation as we progress the different tests so any way the system in automotive and telecom, aerospace, consumer performance, industrial performance will take does not stop at one level of testing the product is going to be evolving again and again requirement is going to be updated modified change the faults are going to be fixed again and again with the different versions different similarities of software different softwares different portable platforms units and all definitely it's a high time for identifying the automation while planning the testing especially this is useful for regression testing where manual intervention is very minimum and not afford to have actually that is where the automation is very important and the test suits which are going to be developed for the automation purpose should be controlled under the configuration so we will try to study what is configuration management test management in the next class next session incident tracking of test cases where different incidents are going to be happening while developing test cases in terms of test approach test strategy bug fixes all this have to be tracked automation best in regression basically as I said automation is very much needed for the regression purpose because again and again people cannot afford to develop the test cases scripts modify and all that and execution especially so you can just use the script what he has used earlier modify according to the need whatever the place he needs do the execution batch execution whatever it is possible regression driven test automation means regression itself can drive test automation where as I said we can use the batch file execution multiple scripts execution as seen some batch execution goes for days where hundreds of problems of test inputs are taken there is a time for execution and all we used to keep the batches for overnight and we see the results next day analyze rerun again keep for days like that so this kind of a automation is very important for regression testing where human intervention is very less required and automation is also useful for incremental development where the development is going to be evolved again and again the next one regression testing test strategy matrix of the relative importance of changes and regression is basically a table analyzed based on how an and then schools can go for different sort of a importance for testing test strategy regression testing here they say as 10% but according to me it should be 2025% but it is in a relative example how they have given based on a particular industry you can see what are the changes for regression that are there in next column and the importance they have put it in the reference so all together 100% is what the test strategy they have try to put it the importance change request could be there 15% change request another one 10% change request 17% 10% defects are there some great defects are very important very less important and their importance 5% whereas defect 1242 is 15% relative importance defect 1243 is 5% importance these importance are subjective based on the type of defects or changes that are needed these defects also can lead to a change request the defects are also called as problem reports so likewise there are different types of categories changes and regression aspects so rest of them they have keeping as 40% including a regression so this is an example so let us see basic problems of regression test maintenance test suite we need to have a test suite which has to be maintained so that regression test can go smooth if i change a feature x how many test cases must be revised because they use feature x so some features are common like a common template or plug and play sort of a module and that I have used in multiple test cases and all that need to be revised just because I have changed the feature x so that is what is the maintenance issue for the regression test which test cases should be removed or replaced which test cases should be added so this also very important criteria for maintaining the test suite because test suite are used to use for regression testing then cost of the retesting how much is going to cost or need to do a retesting often proportional to product size not the chain size basically product size is 1000 if the changes is 1 or 2 it is not going to much cost whereas if the product size is from 10 or 20 and the change size is 1 or 2 definitely the ratio is more and the cost is very high so this also matters big problem if testing requires manual effort suppose we cannot have a automation for certain tests such as assembly level testing or manual analysis etc those kind of regression is very tough in terms of effort because the idea behind original testing the same idea has to be carried out and the people or the resources that are used has to be reproduced and the philosophy is going to be remaining through because the type of testing that it involves is a totally manual and it has to be repeated possible problem even for automated testing when the test suit and test execution time grows beyond the viewers so those are the basic problems of regression test okay so we will try to study more on selecting and prioritizing the regression test cases test case maintenance how are we going to build the build process for regression test and we will try to see an example of how regression testing is been processed in terms of build process in the next class so we will conclude on the regression testing next class and with that we will conclude the unit 4 which is the integration test and the regression test thank you


Kaweza 886 milion doa afrika z In Uganda the potential loss from common techniques of trade-based money laundering specifically over and under invoicing was approximately 4.9 billion US dollars for inputs and about 1.7 billion US dollars for exports in the period 2006 to 2015. Trade-based money laundering or TBML is the process of disguising the proceeds of crime and moving value through the use of trade transactions in an attempt to legitimize their illicit origins. TBML is a sophisticated method of money laundering. It resembles legitimate trade and financial institutions and customs authorities find it the hardest to detect. Some common TBML techniques include over and under invoicing of goods and services, multiple invoicing of goods and services, over and under shipment of goods and services, falsely described goods and services. Criminals use TBML too, loaned at the proceeds of crime or corruption, evade taxes and custom duties, avoid capital controls and sanctions and illegitimately claim subsidies, drawbacks or rebets. Commodities and sectors are vulnerable to TBML when they are characterized by high-value, low-volume sectors like gold. Low-value, high-volume sectors like the coffee and tea industry. Low regulation like agriculture, forestry and fishing. TBML deprives Uganda's government of tax income, which is much needed to provide crucial social services like good education and health care to citizens. The main risk factors for TBML in Uganda include limited understanding of TBML and techniques used, gaps in the policy and legal framework, limited coordination and cooperation between relevant institutions, corruption. How can we mitigate the risk of trade-based money laundering in Uganda, implement beneficial ownership legislation, raise awareness of TBML among private and public actors, improve interagency coordination mechanisms, increase support to frontline agencies, develop public-private partnerships to combat TBML, pass and implement laws with respect to less regulated sectors.


Why being an entrepreneur is easier than being an employee? A few days ago, my company announced on Facebook that we had 8 vacant positions. We immediately started receiving tons of applications. As at the time of making this video, we have received over a thousand applications. How do you choose 8 people out of 1,300 applicants? That's a tough job for me personally, but more so for the applicants because the probability of any of these applicants getting the job is so small, so small that even the most qualified person could be disqualified with a simple thing as how he or she writes the mail. But that's just the first chapter of the dictionary. Even after you are employed, then you'll be given what is called the company's policy. Then you'll be technically told how you must leave your life. Not really so straightforward, but by the time someone tells you when you must resume to the office, the clothes you must wear and in some cases, the makeup to wear. Then that's the definition of a God. Yet, most people think that it's easier to be an employee than it is to be an entrepreneur.  If you're new here, consider subscribing so you won't miss other interesting videos like this. Let's start this way.  Now tell me, which is easier to plant corn or to plant cocoa? I'm afraid many of you watching this video may not see the picture and painting here because you probably have never been to a farm, but I'll explain. You see, it does take about 90 days to harvest corn in my country. It takes as long as 3 to 5 years to start harvesting cocoa. So ordinarily, if I asked you which is easier to plant, corn or cocoa, the answer should be corn, right? Well, you're wrong. What actually happens is that when you plant corn, it grows so fast and in just 90 days, you can harvest your corn. But when you harvest your corn, that is it. It's gone within another 30 days. You have to either eat or sell your corn within one month or it will get dried. However, in the case of cocoa, though it may take you 3 to 5 years before it starts yielding harvest, when it starts yielding a harvest, cocoa can continue making you money for the next 20 years. Job is the corn When I think about the job and entrepreneurship, the best analogy is that of corn and cocoa. To me, the reason why everyone wants a good job is not because the job is easy, better or more rewarding. The two reasons why people love the job is because first, they are brainwashed by the school system to love the job and second, some people are short-sighted.  While growing up, we all knew certain people who worked for banks, oil companies and other big companies. These people dressed well, lived in fine homes and drove good cars. What we didn't know is that most of these people don't like their jobs and most things they used were gotten with loans. Just as when we started envying these people, the school taught us how to become like them. Just study hard and one day, you'll work for a big company. We're Deceived Even for a few people who have the courage to dream of being entrepreneurs, they allowed the temporary pains to make them lose sight of the heaven ahead of them so they decided to plant corn instead of cocoa. Why entrepreneurship is easy for me? For me, if I'm to leave a hundred times, I'll love to be an entrepreneur all of the time because entrepreneurship is far easier for me than a job.  When I say that entrepreneurship is easy, I didn't mean that it's ABC. Instead, I mean if you can leave every day with a picture of your future, you can endure temporary pains. Let me repeat this, if you can leave every day of your life with a picture of your desired future, you can endure most things. The reason why most people think that entrepreneurship is hard is that they want to eat their corn now, today. No, entrepreneurs don't plant corn so they don't have a harvest in 90 days. What entrepreneurs plant is cocoa and that means that they have to wait for five long years before any harvest but when the harvest starts coming in, entrepreneurs often make more money than they can ever spend in their entire life. Let me ask you this, why do you think most people want a job? Well, because jobs start paying you almost immediately. For most people, the number one reason why they can't be entrepreneurs is that as entrepreneur, you may not make any money for many years after starting a business but if you understand what is at the other side of the struggle, then you'll endure the tough times. Student Loan Issue I get it, many people at age 24 have a big problem and that may be college debt if you leave in a country where you get degrees on debt. Most times you just have to get a job to deal with your debt but that's still not a good excuse to plant corn. Ever since I was 15, I hardly can count 100 days when my life was separated from the business. Whether I was in school or working a job, I was always mindful of business. If I couldn't do it full time, I did it part time. If I couldn't do business at all, I read like crazy about it. For me, business is an obsession. You cannot be obsessed about something and anything will stop you from doing it or from becoming successful doing it. Let's compare the pains. This is why I think the most fortunate people in the world are people who get the jobs they love and get paid for 35 years. When I said this, I mean it. You see, employees who get the jobs they are passionate about and which pays their bills are in the middle of the battles of life. The left is hot and the right is dangerous but they are safe in the middle. Unfortunately, that's only a few people, maybe 10% of adults in the world. Whether you want to be an entrepreneur or you want to be an employee, there are pains involved. However, one pain is right in your control while the other is outside your control. Let me explain this. You see, the whole 8 years I spent suffering in the business world was self-imposed. Though I was going through hell because I voluntarily chose the hell, I could smile even when it was difficult. Even though I was broke and frustrated since nobody forced me to be an entrepreneur, I still remained one of the happiest people in the world. That's similar to what most entrepreneurs go through in the first few years of their enterprise. Though it is always difficult, because you look at the mirror each day to see who caused your pain, you can always smile. The opposite is what happens to the employees. A man told me of how he was fired from his job one Friday afternoon. His employer never gave him any notice. I know another woman who lost the job of about 10 years because she stood for the truth. Thousands of people are underpaid, millions are unemployed, several others worked so hard but retired poor. You think about this, if you had to choose between two pains, the pain you willingly go into and the pain someone brings to you, which would you choose? That's the reason why I believe entrepreneurship is easier. Though entrepreneurs go through a lot of pains when starting a business, most entrepreneurs purposely chose those pains, so it's far easier to bear. For the employees, almost every pain that come your way was never expected. I'd rather voluntary go to a tough war than to be caught up in an unexpected battle. Let me repeat, I'd rather voluntary go to a tough war than to be caught up in an unexpected battle. The excuse about capital Millions of poor people all over the world have no excuse. I don't have the capital. Well, if you watch this video and truly like yourself, stop making an excuse that the reason why you're not an entrepreneur is that you don't have capital. Entrepreneurs are not people who turn 50 to 100. Entrepreneurs are people who turn 0 to 100. So if you tell me that you don't have capital, it simply means that you're not an entrepreneur yet. Go and be an entrepreneur and you will know how to turn 0 to 100. How do you become an entrepreneur? Read books about money and business. Stop hanging around negative people. Stop being materialistic. Stop trying to look big when you're small. Stop thinking like everyone. Stop blaming the government for your poverty. Make friends with the positive people who believe that they can change their financial situations and be willing to make sacrifices for a few years. Entrepreneurship is about turning 0 to 100. True entrepreneurs don't complain about the lack of capital. I'll conclude this video here so that it won't be too long. If you want me to speak further on this topic, kindly let me know in the comment. If you plant corn, it will grow fast but the harvest won't last. If you plant cocoa, it may take a long time before the harvest but the reward can last forever. Thank you so much for watching our videos. Are you between the ages of 15 and 40? Then we invite you to join our new channel which was specially created to share with you inspiration and life's lessons to succeed in life. We call it Under40 TV. Kindly look at the description box to join the Under40 TV. We love you.