Showing posts with label Testing. Show all posts
Showing posts with label Testing. Show all posts
Friday, 13 November 2020
Wednesday, 15 January 2020
Smoke Testing VS Sanity Testing With Example
A lot of Sites writing articles which are making students of Software Engineering confuse between Smoke Testing and Sanity Testing by stating that these are two things which we can use interchangeably. Trust me you cant if these are two same things than why Different names?
Don't get into trap, learn the difference so it may help you in the practical market as a Software Engineer.
Software Testing is something on which the Quality of the software depends a lot. If we are not clear about even the types of testing than I am really worried about the quality.
Smoke testing is general abstract level of testing, If you develop a software with 10 features after completing the development you may test those 10 features on abstract level if they are working fine or not read my word carefully you may test those features on abstract level, means you are checking all features on abstract and not performing in depth testing of any feature so it is smoke testing.
Now when you were performing the smoke testing on that time you found some kind of problem in any feature or say in any module of the software you report that to the developer of the software.
Now the developer will made some changes to the code to fix that issue and report you back that the Issue has been resolved. You will check that just for your personal satisfaction, That checking is actually sanity testing.
Look there is a huge like huge difference, Don't mix these two things with each other.
I usually take help of daily life examples to clear the concepts fast.
I usually take help of daily life examples to clear the concepts fast.
Let me give you one example, You take your new born to the doctor, although He looks fine to you but still you care a lot for him you took him to the doctor for general check up, The doctor will stick to his throat or any other body part by saying I wana make in depth checkup of throat. He will made the general checkup of all his body parts from head to foot, He will make it sure that all the body parts of the new born are fine.
Now what happens when He was making a general checkup He suddenly notice something wrong in the eye of the new Born He recommend you some treatment and carry on the further general checkup of the body.
Now what happens when He was making a general checkup He suddenly notice something wrong in the eye of the new Born He recommend you some treatment and carry on the further general checkup of the body.
You will come back to home follow the treatment prescribed by the doctor and visit the doctor again on the completion of prescribed treatment.
This is your 2nd visit to doctor now. The doctor will direct approach to the eye of the baby and check the if it is fine now after the treatment, now He is not checking all the body parts He is specifically checking the eye to check if it is fine after the treatment or not this is Sanity Testing.
All the things doctor did in the 1st visit fall under the category of Smoke Testing and what He did in the 2nd visit fall under the category of Sanity testing.
Now this is the Example which will help you always to keep remember the concept of testing all the time.
If you can understand easily Urdu - Hindi Language above video lecture can be beneficial for you.
you can download short notes to this lecture by clicking the button below
All the things doctor did in the 1st visit fall under the category of Smoke Testing and what He did in the 2nd visit fall under the category of Sanity testing.
Now this is the Example which will help you always to keep remember the concept of testing all the time.
If you can understand easily Urdu - Hindi Language above video lecture can be beneficial for you.
you can download short notes to this lecture by clicking the button below
Tuesday, 7 January 2020
What is the Difference between Bug, Error and Defect - Software Engineering
Software Engineers, testers and Programmers use these terminologies interchangeably without knowing that these are different things.Error: If I write a program which is not getting compiled due to the mistake in syntax that is known as error.
Bug: If program is ruining but there is deviation between expected result and actual result that is due to bug.
to get more detail about this topic watch the complete video lecture.
To download the slides shown in video lecture click the button bellow
Thursday, 7 November 2019
Def: It is the process of modifying the software after it has delivered to customer.
But why we will modify after the delivery?
Ans: There can be different reasons we can modify the software for the improvements, We can modify the software to correct the faults captured by the customer/ End-user.
Need of maintenance:
We may feel need of the maintenance for the following reasons
- Interface with other system: May be our software is working in a the environment where after some time the company feel need to link it with other system so we will modify it according to company requirements to make it interface able with other system.
- Correct the faults: This is the most common reasons to update a software. That is fault correction and every computer and smartphone user know that we receive updates on our mobiles and OS in computer almost on daily basis which claims minor bug fixes and all that some time we do this when software start working in the practical environment and start showing bugs, to fix them we perform maintenance.
- Improve the design: This is another reason, have you ever notice facebook, Google Play (android app store) they always keep changing the design this is also the maintenance type or you can category.
- Implement Enhancement: May be company like the software you develop for them and they want to add some more features into it so they will call you now its your turn to add some enhancement now it will fall under the category of maintenance.
- Security patches: If the software is sensitive, security would be priority so Hackers keep finding new and new ways to get into your software and you keep closing the doors off for the hackers into your software those methods you use to close the doors are known as security patches.
Categories of Maintenance:
- Preventive Maintenance: In this category we always try to predict the problems that can create issue for us in future and we try to over come those problem in advance.For Example: Our researcher see the software is getting slow when more than 10 people are using it through different nodes but the software is designed for the 50 people, it means if it is getting slow on 10 users so when it will reach its maximum limit it will stop working or perform badly so the developers of the software take action instantly before the number of its user reach up to maximum limit.
- Corrective Maintenance : sometime we found a big which is disturbing the working of the software we found that and try to remove it instantly to put the software back on smooth working is called corrective maintenance.
- Perfective Maintenance: New features keep coming in the software industry on daily basis, Your software should remain compatible with those or it will be outdated, to keep your software compatible you need to perform prefective maintenance.
- Adaptive Maintenance: May be your software is the first love of your client but He is moving from Windows to MAC OS and want to keep using the same software now you have to make changes in the software to adopt the new OS environment that is know as adaptive changes.
Keywords:
software engineering,software maintenance in software engineering,software maintenance agreement,
software maintenance process,software maintenance tester,software and testing training,corrective maintenance definition,
perfective maintenance definition,adaptive maintenance definition,What is Software Maintenance,
software engineering tutorials,software engineering lectures,software maintenance process model,
software maintenance process,software maintenance in software engineering,Software maintenance,
Tuesday, 5 November 2019
What is software quality? What are the factors in which software quality depends? this videos is good for software developers, software users so they can analyze after watching this video if the software they are using is good in quality? if the software they are developing is good in quality? No tools are required just basic things to check software quality analyze by yourself your own software.
We assure you we will clear your concept of verification and validation in Software engineering in this 8 minutes videos. Software verification and validation in software testing is a an important part of the software engineering but due to some confusing way of teaching students remain unable to understand it. In this video we try our best to deliver you properly the concept of Verification and Validation in your own language Urdu and Hindi watch the whole video like the video if you understand it, comments your reviews about the video and subscribe the channel to get more informative videos like this. The video will provide the answers of Following Questions: 1) What is verification in software engineering? 2) What is validation in software Engineering? 3) What is the difference between verification and validation? 4) Which one is better verification or validation in software engineering? 5) Who perform software validation and verification? 6) what activities are involved in Software verification and validation?
✅The concept of coupling and cohesion in Software engineering a very short video. 📌Link to detail video on Coupling and its types/Levels. https://youtu.be/qVR6ShVPObc 📌Cohesion and its level detail video is available on the following link: link: https://youtu.be/u6yEBxlJMJM
case tools are most discussed thing is software engineering, this video will tell you what are the case tools in actual what are the categories of case tools and how they provide ease in working. The video is providing the answer to following questions: 1) What are case tools? - Answer at 1:582) CASE stands for? - Answer at 1:26 3) what are the categories of CASE tools - Answer at 2:084) some examples of CASE tools - Answer at 2:55 It is humble request to like our video and subscribe our channel: https://youtube.com/SoftwareEngineering
Brief: This video is about the detail difference in white box and black box testing with an example. It is god for the new students of the software engineering and it is good for those who know about White and black box testing as well as it will clear the concepts of testing in details with example.
Key Points : Black Box: The method in which internal structure of the Product is not known to the tester. White Box: The method in which internal structure of the product is known to developer. Difference: - Black Box: The Term black box is used because we do not look inside the application technical working. Programming knowledge is not required for it. It tests from the end-user’s perspective. Input and Output are tested and checked against the expected outputs. Programming knowledge is not required. =============================================== White Box: The Term white box is used because we can look inside the application technical working. Programming knowledge is not required for it. Developers test the application in White box testing. Internal functionality is tested here. Programming knowledge is required here.
Brief: This video will provide you the answers of following Questions. - What is Software Testing? - What is Test case in Software Engineering? - How to make test case in Software Engineering? - Practical example of Test case in Software Engineering?
-Brief: This videos is about the software testing myths and realities, We believe with closed eyes on lots of statements we consider them universal truth but actually they are just some myths. we discuss some most common myths in this video. Myth # 1 : A Tested Software is Bug-Free Myth 2: Testers are Responsible for Quality of Product Myth 3: Testers only task is to find bug Myth 4: Complete Testing is possible Myth 5: Testing is too expensive Myth 6: Testing is time consuming
Brief: This video is about the Software Testing Life Cycle how the life cycle of testing should go through in the testing phase of any software. It is recommended to watch Software Development life cycle video to understand in more better way link to SDLC video is Link: https://youtu.be/wEiatXC52Qw We have also discussed about RTM - Requirement tractability matrix tutorial here is the link for that tutorial Link: https://youtu.be/_0gREjb-ibI
Brief: This video will explain to you what is manual testing and what is automated testing also tell the advantages manual and automated testing more over it will guide you wen to chose automated testing and when to chose manual testing. ===================================================== Links to Other testing Videos: Software Testing Life Cycle https://youtu.be/vZbFp_awYcA Software Testing Myths https://youtu.be/LBBYdBXYac8 HOw to write test case: https://youtu.be/4FBDTuWLFCs Black Box vs White box testing https://youtu.be/96JZf4gwnBk
Brief: This video tutorial is about Automated testing tools for web applications. It is just to introduce you with the tools available online to test your web applications and I am sure it will help you a lot.
Brief: This is video lecture is about what is gray box testing in Software engineering | Software testing, Most of the people know about the black box and what box testing in software engineering but they do not try to learn about the gray box testing you don't need to think or focus to much just listen this video and all your concepts about gray box testing will be clear. This video going to answer your for the following questions: 1- What is gray box testing? 2- How it is different form white box testing? 3- How it is different from black box testing? 4- When to use gray box testing? 5- When we should not use gray box testing? Note: Sorry I forget to remove the sentence explanation of spiral model from 1st slide
✅Brief: This is the video about what are regression and retesting in software engineering. It consist on practical example also to clarify your concepts as well. 📋This video will clear you concept on the following things: 👇 ✔️ What is Regression testing? ✔️What is retesting? ✔️When you should use regression testing? ✔️When you should use retesting? ✔️What is the difference between regression and retesting? ✔️Practically demonstration of regression and retesting?
Monday, 4 November 2019
✅Brief: This video explains what is alpha testing, what is beta testing and what is the difference between alpha and beta testing, watching this video will also clear your concept about which testing belongs to which category e.g. if alpha testing is black box testing or white box testing same for beta testing. 🚩 Lots of books are describing this topic in very good manners but sometimes you need a person to tell you how things work so it will solve this problem and video will help you in understanding. 📋This video will clear you concept on the following things: 👇 ✔️ What is Alpha testing? ✔️What is Beta testing? ✔️What is difference between alpha and beta testing? ✔️Is alpha testing black box testing or white box testing? ✔️Is beta testing white box testing or alpha testing? I am sure listening to these video lectures will help you a lot in clearing this topic.
✅Brief: This video will clear your concepts about what is the software Smoke testing, from where we got the concept of smoke testing and how it works. 🚩 Lots of books are describing this topic in very good manners but sometimes you need a person to tell you how things work so it will solve this problem and video will help you in understanding. 📋This video will clear you concept on the following things: 👇 ✔️ What is Smoke Testing? ✔️How smoke testing works? ✔️From where we got the name Smoke for this testing? ✔️How to smoke test the software? I am sure listening to these video lectures will help you a lot in clearing this topic.
