so, for the test link along with the assignment of the roles we can also have some key word management and platform management platform management is something like how we want to set up the environment like the test bed or the various platform that we want to test it something like say we have a Firefox we have a internet explorer we have a mobile we have a PC so detail of the PC we can add something like OSPC having IDE setup this is what we want to have a platform so this is been set for this project similarly you can create your own and try to export it to document or something like that so that is what we can do with the platform management the next one is the inventory so inventory you know for this embedded project what are the materials or the configuration that you want to have it so we can create something like I have a PC with code warrior IDE then we have we <IP_ADDRESS> owner is embedded software testing for the first set of the embedded test environment hardware that we need to connect for this is the MPC 554 target board connected with BDM or the JTAG so it is a connector any special nodes that you want to have it you can have it so you can save it you see that there is a code warrior PC with IP address being set up so this is how we can add the inventory okay so once the platform test bed and test environment is set up we can start with the requirements because requirements we would like to add to our testing management so here you can see the folders the different directory structures where the repository is existing and all that so you can create your own test project okay so under this we can have our own or you want to create you can create a new one document eddie, ESD test project same title we can put status is a drop stage you can have different status like that this specification is under draft review rework completed it is valid not a stable for each of this specification we can have requirement type it is a informational feature so use case type of requirement where we use it in model based design then interface requirements non functional constraint etc so it is a feature let us say requirement specification type it is a section of that or user requirements specification system requirements system requirements specification expected number of test cases for example we will take the mode only I try to understand okay I have opened the test case document before that we need to understand the requirements right so it is a part of this only so we will try to open that so this title is out some requirements like SRS2 and test cases for SS2 is about 10 so we can specify here it has number of test cases expected is 10 and has relation it did not be for that document first time itself while creating test cases you can tell that I may have test cases of 5 6 10 whatever you can rework that and update it but that is the initial plan so which can be reported so any relation that you want to have for that you can have it like this relation or this feature is related to something else we can create it the defect ID if anything is required you want to I can add it so that is how we can create it so you can apply this is going to have it under this you will see it is getting created under the test project main folder okay the next one is a document ID so you want to have a document ID for the corresponding thing so we have a document called SRS UI same name you can keep it software requirements specification for UI maybe you can expand if you want okay so now scope scope of that specific requirement you can have it we can have this say modes of operation we can paste it here SRS2 just copy it for example let us see what happens yeah it has pasted that particular SRS it is not SRS1 it is what 2 since it is a automated from the world document so let us try to create this so type of this user requirement specification system requirement specification and we will say this okay so you can see requirement specification this has been successfully created similarly next one you can create it or you can edit the existing one also suppose you want to edit that let us try to go to the software requirement for UI here we have created you can see the last one being created with the specification you click on that so the main folder we can see the revision one you want you can update or add first division it has created with software requirement specification modes of operation is this if you want another one you can create it or you can maintain it the existing one okay so once we have if you want to attach you can choose file and import it from that whatever it is we have you can give the title and it will like import it to the entire test linker server okay so once we have created the software requirements for that particular software requirements we can have a requirements overview we can see here there are different requirements its title is here version created last modified the frozen or not coverage whether it is there or not you can have a pending type status all this typical attributes of the software requirement specification so that is how we can see the overview of the complete requirements the next one being you can search requirements if you have multiple requirements and you are trying to look into some requirements you can search the requirements or specifications then you can assign the requirements to a specific test cases or test case ID first we will try to create test cases then we probably can try to assign those requirements so that will be better okay now having said that the requirements have been created we can go ahead with the specification it is not testing probably we can try to see any of the tests that we are interested to okay we can accurate our one test case ID is 0 1 title so we will go through the test cases example and try to provide it so this is a modes of operation is a title so we will try to put this here there is a suit anything that you want to identify that suit you can make it as functional testing any key what you want to add you can add it status is same it is a draft importance it is very high it has other options like medium low what is the importance of this specific test execution type you want to have a manual or automated you know that two types of testing can be done on the target mode so this can be tested on the target mode so except to the result is okay so we will go through the test case one example and we will know the expected result and all that okay so fail mode expected result is the fail mode actual result when we execute only we will come to know test case description we can add it something like to test the modes of operation test case ID it can be same as this 0 1 or specific test case ID you can use something like this we should be unique actually for each of the test case so any defect ID that we have found we can identify but before execution it will not know what is the actual outcome so we can have leave it and later update it so once we have this we can apply it so that the test case is corresponded to this gets added so it is getting try to insert the test cases into this and in case you want you can choose a file from directly from the test case and add it here into this project anything can be done the either it is create the test case which we have created okay test specification under what we have put so test one so for this this this so dependencies no functional testing did we add this okay so it has not created so let us try to create one more so we will try to create test case ID again first test case modes of operation test suite is it can be any test suite something like a functional testing let us try to name it and keyword anything you want you can add it advert as anything that is all created by the admin when you have created the project so one of them you can select let us not select anything importance of this test case it is under sorry status of this particular test modes of operation is something like a draft it ready for review review in progress rework absolute something like that so let us make it as a draft then importance of this test case high medium low pre-type of importance we cannot say can make it as high execution type it is a manual or automated we can make it as automated you can set the expected result something like fail mode because we know that test example we have created the expected result is fail we are going to put it here actual result we do not know because we are not executed it test case this description we can add it something like to test the modes of operation so particularly we are trying to test SRS 2 it is fail mode right we can add that detail fail mode test case ID same thing what we have created for the first case we can add it here defect ID we do not have a defect right now you can have it later stages once you are done we can apply this so this is going to be effective for that particular test this project example it should be listing it let us see okay so once we have the test cases specification done then we can add test cases similar to this sorry test cases we can search if you have multiple test cases by filtering what is the title what test cases I am interested what it will display that particular one so we will try to search this one say find whether it finds let us see AB some already somebody has created that is visible we can try to put this and it will display the test case that is created for here and we can see that way okay so there are many options in terms of adding modifying deleting but most of the time the deletion and modification will be done by the authorized people authorized people in the system deletion can be done by admin and addition modification can be done by the test designer but he will have to do a versioning why because he has to control the specification so there is a revision involved for that so every time he creates or adds it will become a new revision this is how we can see it there is another option called test case created per user so we can see how many test cases have been created by what user so let us try to understand the user called EST we have created for example we will try to filter by this and try to submit the query it should list okay no results are there we try to add test case somehow that test case not got added let us see why it has not added maybe the permission may not be there a functional testing I thought I have added not this one okay so test specification so in terms of a test specification we can add and we can assign a test cases and the requirements we have seen the next one is a test plan like you want to add different builds for this test plan we can do the test plan management with the help of that like we have studied about this in one of the sessions in terms of how the test plan should be and the load I think okay so likewise we can see the test plan management details and test execution like we can execute test here execution means basically with the builds that we have we are going to assign some people and add the test scripts and those things and similarly if you want to create a test script execution linked with this we can create it but basically it's a static way of doing this the execution build where we will add the execution details of the specific test suite if it is active open any dates you want to mention you can mention you can create it so this is a build it's going to have it if you want to you can attach files also so it will be added into that actually so you can see it is listed out here so that specific thing having said that we have done the build management of that particular test execution so you can see what are test cases are going to me if I have logged in as a user I can see what are test cases that are assigned to me and once I execute I will move to the next stage saying that I am going to execute and report it see one example they have so for me there's a build BBB one item is added here I am responsible for doing this test this is a test one there is a black and yellow some test is there it's an example okay the next test reports and metrics so you can see the reports in terms of test execution it's a status and all that so for example test plan report you can see you can filter any of these things and see the report you can see test plan design report project project plan project suit likewise so we have seen this particular one project then we can see test report similarly you can see some metrics in terms of how it can be reported to hair management or what are the specifics of that particular project like overall build status if you have done like the builds are assigned and the build is not executed or executed failed passed complete report can be generated here you see this top level test suits there are two two are not run so 100% pass fail is not generated yet because it's not executed according to test priorities also we can see it as well as by test per build also we can generate test case assignment for you we can have it so test cases without test or assignments so various metrics can be reported this way by clicking that particular items so it will show that this particular test case is not executed this way it will show some charts for interstate can also be created in terms of pie chart or overall metrics like what are the tests that have been run or not run for this project is showing that not run is 2 that means showing as 100% not executed so similarly top level suits in terms of results test suit and the numbers it can show the pie chart depending on the type of metrics that we want so finally we can generate the requirements based report which will report for each of the requirements what are the tests that have been done you can see under this umbrella test project 4 6 1 0 there are different types of test cases having different importance and these are all test cases not assigned to any of the test plan just basically test is created so once you link that it is going to show what is been linked so that is how we can generate the reports and metrics of different tests that are under similarly we can add some margin test in terms of priority we can assign test execution and you can create a version for this so that is how we can use different projects and see it more example we try to understand so there is a metrics dashboard that is part of this test we can see the progress is 50% it is 4 out of 8 tests have been executed so far not only is another 50% passed is 1 out of 8 that is 12% failed is that is 1% blocked is 0 so those specific test cases in terms of progress for each of the test plan you can see the metrics this can be exported using the export option and there is another option in terms of failure pass and all that once you have executed I think that means you need to add it so you can link to bugzilla bugzilla is another similar tool where we can monitor track and report the different bugs that are come out of this particular test link activity so both can be correlatively linked so that is the purpose of bugzilla bugs and all can be tracked and managed with the help of that actually so that is how we can use the test link by creating the various requirements added to here test cases you can edit it you can manage the test cases assign the users and add the test execution aspects and create the reports and metrics out of this test link so totally it is a test management tool this can be used and revisions also can be created so that this can be under configuration okay so the basic thing about this link is we need to have the workflow created for the test link like initial step would be to create a new test project and assign the particular to have it so step to assign the testers or engineers with the tasks then we need to copy paste the software requirement specification or you can import certain imports it supports like doors or any word documents or excel sheet so it will create test cases with the empty test cases so we need to reorganize them into test suits then create a content for empty test cases using test specification that are being organized into test suits test suit is something like having organized test cases correlated with the test case then once we have this we can create a regression testing and assign application applicable test cases that means where we see there is a change or there is a failure and we need to fix and re execute those things we can create under regression testing so that next time we need to work under the regression testing folder only then we are going to create a plan build and that link all test cases in the test suit that particular test plan then assign resources to that test plan so that those resources are responsible for particular test cases then assume QA got this first build of release or candidates from developed team execute and record the testing with the result so basically we are going to evidence the execution and record the pass fail results into this next step is assume QA get new build because the first build what a issue we are going to have a regression now so this blocking issues we need to re execute or regression test to make sure that those tests are been passed if it is not passed we are going to report it to the higher side higher management saying that this many percentage have got passed and failed etc will next step would be the manager of the test lead and other project related stakeholders want to see the results and status of testing then these stakeholders including managers can create a accounts or they can have view of this using the default guest or any other account with a privilege to view the test results and generate the overall report of the progress of this suppose new changes happens to the existing functionality is easy to modify existing test plan and add new test cases if you want to add so that the robustness and all that can be taken care test suits continue to execute as usual by generating various reports so for new project again QA creates a new test follows about the steps to implement for the test link so these steps is nothing but the testing or workflow with the help of this we are going to create the testing project test management and report it so that is how we can use it okay so so with that the practical sessions of embedded software testing we will end we will try to look into the exercises so that you will have an understanding of all the theoretical and practical aspects of embedded software testing few of the examples I have created here I will circulate it once all these tests objective questions are completed I will just walk through few examples in terms of theoretical as well as practical things okay so out of four levels these are objective type of questions we need to answer any of these four out of four levels of testing below which one is mapped to acceptance is the requirements is mapped or architecture design relevant design code so you need to choose one of this similarly we have from the levels of testing will be missing one out system testing acceptance testing component testing so which one is missing in this is it regression is missing integration is missing third one is what is the other context type of test for static testing is it a maintenance testing centralized testing integration or dynamic what is the other context type of static testing same question which additional test level could be introduced into a standard V model after a system testing system integration testing acceptance testing regression testing component integration testing okay so like this I have about another type of word objective question where there is a fill up fill in the blank is there out of this four you need to fill it up for example avoid bug testing technique that executes possible combinations of condition outcomes in each decision is what the condition coverage or decision condition coverage decision coverage or statement coverage okay but the next type of objective question is a statement sort of a objective question where which among the example which among the following is the correct sequence to test execution so all below or identify test cases and test sake execute test scripts setup environments review the test cases the next type will be setup test environment identify test case review test is that execute the scripts set up test environments identify test cases test cycles execute the scripts review test results okay next type of objective is which of the following validates that multiple parts of the system interact according to the system design unit testing user acceptance testing integration testing system testing next type of objective question is there is a flow diagram of a embedded system program so what is the minimum number of test cases we want for 100% statement coverage and 100% decision coverage respectively so we need to answer one of the like statement coverage is one decision coverage is three or two three two two or three three one of this will be answer for this so we need to understand this flow to understand the adjust nodes based on that we are going to have statements how much minimum statement coverage we can have how much minimum decision coverage we have you know there are two decisions here and there are few statements okay so what does the test design begin in Sdlc the testing phase low level design phase high level design phase requirement phase which technique is used to test case designing what the value of this equivalence particular or integration testing we have what how do you track the requirements in test cases when should you stop testing okay this is due to change the design so what is the impact where we are going to test it next one is about testers insert additional code into a program to collect information about the program behavior during testing what is this called as defect density is calculated this is about test matrix so all sort of tests that we have covered in theory and practical I have got few questions so with that we will end the embedded software testing questions I will circulate the PPT and the questionnaire so that you can answer those questions accordingly so there is a list of questions in general or complete embedded software testing so there are about 35 questions that I had put it here you can go through this also like it is a basic about embedded software testing that methods so whatever the five units that we have covered for embedded software testing all the questions have been listed out here there are about 35 questions so this we need to answer based on what we have gone through in all the sessions earlier for example about the general V model how it is applicable for test methods and why we need test plan what is the PEM method is all about then I have a question I mean about brief sentence about test harness test bench fault injection I input output ICD break point simulator emulator eyes profile so basically there are embedded system basics if you are able to answer that means you are a good tester in terms of embedded software testing so similarly we have prototyping life cycle V model significance of nested V model what sort of systems we need white box and block back system what are the advantages how coverage is defined in the common space testing similarly why it is called as V model how coverage is defined likewise we have about 35 questions or embedded software testing


What's going on guys? It's your boy DPJ here today with another Destiny video and in today's video we're going to be talking about challenge mode and what this is. Now info at this moment in time is at a minimum and what we have to go by isn't much more than a few comments from the bungee dudes as well as a few details coming from that Edge magazine. Now this all started a while back before The Taken King was even released. Luke Smith made a interesting comment which had many people including myself speculating as to what it is. Most as well as me thought it was going to be a third mode and I think we were actually right. Let's recap on what Luke Smith actually said them two months ago. Caught in Luke Smith here, we developed hard mode first this time and scaled it down to normal mode and we have one more thing we're not talking about yet that's pretty sweet. It's a twist I'm excited about. It's clear now that Luke Smith two months back was indeed talking about this new challenge mode. Now in the recent UK Edge magazine Luke when asked what else is left for us players to discover Luke Smith answers with this. We have a little more left in store for players in hard mode. All of the boss fights have a new mechanic, a new element.  Mathematically you've only seen or completed five-thirteenths of the raid. Now Bungee tweeted this in response to a tweet made by more console. Challenges are coming to Kings 4 soon both normal and hard. For now we're working on how they reward you. In reply to that tweet Luke Smith tweeted this raid challenges are not currently active. The final three fragments are among their rewards more info in several weeks. So challenge mode that in itself tells you that this will be a third mode for the Kings 4 raid. Normal, hard and challenge. Challenge mode I'm guessing will be the options of the three main bosses War Police, Golgoth and Oryx. Obviously selectable on either hard or normal. These as Luke Smith said will offer special rewards such as emblems and fragments. Obviously one fragment obtainable from each of the bosses giving us the three remaining fragments we can't currently get. I believe some if not all of these emblems that are rewarded from this challenge mode may be visible via the emblem votes but Bungee did state they are working on rewards for this challenge mode so obviously more rewards will be implemented into the reward system of this new challenge mode. What interests me is the final three remaining fragments and here is why. I could be a million miles off but this is just my opinion and why I think. Now we all know that before the taking king was dropped Bungee, Luke Smith and many of our great sources talked about 50 hidden parts on that dreadnought that uncovered a weapon. It definitely 100% was 50. I've heard it from Luke Smith's mouth myself. Now many people forgot about this and associated it with the 45 fragments needed as part of the touch of Malice quest. I never and I still think that is still a hidden weapon left for us to discover. I mean think of it this way if you compared DLCs or previous raids they all had that raid weapon the vex from the water glass the necro chasm from the crawlers and raid the Dregs promise the Queen Recker's bow and a lot of wolves from the Prison of Elders. I know a lot of people will be saying the touch of Malice from the Kingsfall raid but I think differently and there is no denying that the taking king offers way more content-wise with the raid. I find it crazy to think that there isn't any other weapon for us to discover with all the new content that keeps coming and what we currently have. The challenge mode offers the final three fragments to complete the 50. I believe these will trigger a new quest for a weapon unknown to us yet but that's just my opinion either way it will be several more weeks before we find out any more info about this challenge mode and when it's dropped. But if anything else comes beforehand you guys will be certain to find it here on my channel so subscribe if you're new. Guys let me know what you guys think about this and your opinion on what challenge mode will be down below in that comments section. Hope you guys enjoyed the video if you did do drop a like or do appreciate the support I'll catch you on the next one and peace out until next time. POST! POST!


Loggers jump when they see what dog is doing in tree. It was like any other day for the loggers of Georgia Craft Company. Their job was to procure wood for the company's paper mill machinery business, which would later be turned into paper pulp. That day, they were assigned to a forest owned by the company in Jasper, Georgia. They arrived, set up their equipment, and began selecting the trees that would be cut down. It wasn't any old kind of wood that they were there to obtain. The area that the loggers had been assigned to was an American chestnut forest. This type of wood was almost decimated during the early decades of the 20th century, thanks to a ravaging fungal disease. But it was a strong wood and it managed to survive in eastern North America, from Alabama and Georgia to New Hampshire and even Nova Scotia. It was a fast growing type of wood, faster than oaks, so this made it commercially valuable. But on this day, loggers were about to find more than wood in one particular tree. The loggers starting chopping down the trees that had been pre-selected. Then they came upon a chestnut tree that looked like all the others. But once it was finally cut down, they realized something was not quite right. Inside, the trunk was hollow. This meant it would produce less wood for them to take back to the paper mill. But they'd already spent time cutting it down so they proceeded to chop it into logs. However, they had to stop once they discovered something else. It was not just that this tree was hollow. There was something inside the hollowed out trunk. It was dark, so the loggers couldn't quite make out what it was. They got on their knees and leaned closer into the trunk. That's when they saw it the object inside the tree trunk was an animal. A rather gnarly looking animal. The loggers hath expected it to jump out at them at any moment. But the closer they looked, the stranger the situation seemed to get. The loggers finally figured out that the beast inside the hollowed out tree was a dog. But it didn't look like a normal dog. The animal was dead, but it looked like it was frozen in place, with a growling expression on its face and its paws in a climbing position.  Now it was up to them to decide what they would do with this remarkable discovery. The loggers job was to collect the wood from the selected trees and bring it back to the paper mill. But now they were faced with a once in a lifetime discovery. They had the choice to leave it there in the woods, or cut it open, and take the remaining wood with them. But they decided this was too extraordinary to destroy. So, instead, they set out to find someone who would know what to do with this mummified dog. That long after, the loggers caught wind of a new museum that was set to open in Waycross, Georgia. It was called Southern Forest World, and it was dedicated to the forestry industry and the southeastern part of the United States. Its exhibits would feature the history of forestry and woodwork since colonial America, and all the way to modern tree farming techniques. The loggers thought it might be the perfect home for their discovery. The loggers donated the hollowed out chestnut tree with the mummified dog inside to Southern Forest World. Months later, the museum officially opened and the dog became quite a popular attraction. But many people thought it had been man-made. After all, most people know mummification as the process the ancient Egyptians used to preserve dead bodies. It can't occur naturally, can it? Southern Forest World called upon experts in biology and anthropology to explain how this dog inside a hollow tree had ended up so well preserved. Christina Kilgrove, from the University of Florida, came to the museum to inspect the remains of the dog. That's when she was able to shed light on the process that had resulted in this animal looking frozen in time. When an animal dies, the process of putrefaction occurs because internal and external bacteria start consuming the dead tissue. They grow, they reproduce, and they start taking over the body, said Kilgrove, who was a tissue decay expert. But there are certain phenomena that can stop the microbial activity. One of them is dryness. And it just so happens that American chestnut trees contain a chemical called tannin, which acts as a desiccant, and it's what prevented the dog's putrefaction. That said, how come the carcass wasn't eaten by other scavengers? There are several scavenging species in the Georgia forests, including vultures, raccoons, and coyotes. Many of these could have found the dead carcass and made a meal of it. Except for the fact that they never knew it was there. Bertha Sue Dixon, director of Southern Forest World, explained that the hollowed-out tree trunk had an accidental chimney effect. The air blew upward and dissipated, never carrying the smell of dead flesh to potential scavengers. Anything that would eat dead flesh would never know he was in the tree, she said. After this explanation, one mystery remains. After experts examined the dog, they determined he was likely a 4-year-old hound who had died about 20 years before the loggers discovered him. They speculate that he was chasing a raccoon or a squirrel that climbed up inside the hollow tree. He followed the creature inside and managed to climb up 28 feet before getting stuck. Unable to get back out, it died of starvation. And though his end might have been sad, his legacy remains. From the beginning, the mummified dog was undoubtedly Southern Forest World's most popular attraction. The museum staff decided to give him a place of honor in the center of the main building's rotunda. Visitors loved to take photos with him, and his picture is used in all promotional materials for the museum. Eventually, they decided this notable dog should have his own name. Staff and visitors knew the creature as the mummified dog. But eventually, that didn't seem like enough. So the museum decided to hold a naming contest for fans of the attraction. A lot of people submitted their suggestions, many of which were quite clever. Chipper and Dogwood ended up being the runners-up. But the grand winner was Stucky. Nowadays, if you want to visit Stucky, all you have to do is make your way to Waycross in Southeastern Georgia.