Use Case Testing-Use Case In Software Engineering-Use Case ATM Machine-Use Case ATM-Use Case Test

[@SimonTubesc]

17 minutes but I get two weeks worth knowledge... tnx

[@dvassup]

Play it at 1.5 speed :) even faster knowledge.

[@adebowaledollars1]

@@dvassup so, I am not the only one who does this, I am a completely normal person.

[@bridgetborders1452]

Thank you so much! I just poured through quite a few videos and this is by far the best. Really helpful for my project.

[@QA1]

Bridget, great to know. You can view all my Test Design tutorials at kzbin.info/www/bejne/q6rHcqygprmGn9k

[@jimioutback]

Thank you: clear and concise explanation, and the examples were very helpful.

[@QA1]

@jimioutback - Glad that you liked the examples. Thank you for your comment.

[@srilakshmichirumamilla4918]

Thanks for the Upload the Use Case Testing video, I watched all your Manual Testing videos, it's very simple and easy to understand even Non IT people also

[@QA1]

srilakshmi chirumamilla Yes, I do try to keep it simple and practical. Please subscribe to know about the new videos. Regards, Inder

[@cherukurusable]

Hi Sir, Can i get ur email id or phone number, i would like to take Selenium training

[@opalhazels42]

yes, very useful videos. I watched all black-box techniques you described. i find that you explain things in an easy-to-understand and right-to-the-point way. much clearer than my reading material :D thank you!

[@TheFfgo]

clear explanation, thank you

[@dominicankendry]

I know this is an old video but you just got a new subscriber, nice job!

[@QA1]

@Kendry Jordano - Thank you. Welcome to the Software and Testing Training channel. Regards, Inder

[@bandipratima]

Thank you, no confusion. clear.

[@higiniofuentes2551]

Thank you for this very interesting video!

[@nataliianataliia2442]

Good examples and explanation. Thank you!

[@QA1]

@Nataliia Nataliia - You are welcome! Thank you for your comment!

[@vasukiani3563]

waah ... yua explanations re 2 gud.. got gud clarification aftr wtcg dese videos... wud lik 2 hav more real time examples... congrats nd thank yu for this wonderful job....

[@Swami9827]

Thank you for exapling what is exactly use case is no one will go through deatil explanation like you

[@QA1]

@Shambala Swami - Thank you for your awesome comment 👍 I really appreciate it. - Inder P Singh

[@vishalprajapti8996]

Excellent Video, you have done an amazing job.

[@QA1]

***** Thank you, Vishal. You may like my other videos in my playlist called Test Design at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc

[@esraashokry8866]

Thank u so much....very useful😊😊

[@KomalYadav-di3qz]

Delivery of content is very awesome , simply explained thankyou sir

[@QA1]

@Komal Yadav - Thank you for the awesome comment. In Use Case Testing, we should remember to test both the normal workflow and every alternate workflow. Regards, Inder

[@ryentertainmentbulletin]

Thanks for helping beginners . Your teaching trick is really good

[@QA1]

Thank you, Sumit.

[@LearnEnglishVD]

Nice tutorial. Thnx!

[@anisul-islam]

Thanks. I found this very helpful.

[@QA1]

Thanks. You can check out my other test design tutorials. The link is kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc

[@malathisaravanan28]

thank you sir

[@Swami9827]

And I think this is very very .... Helpful to me

[@kaminisenthil3606]

Very helpful and well phased 👍🏽

[@hygia1540]

Nice video. Thank you

[@louisv82]

Thank you. Very helpful :)

[@higiniofuentes2551]

This is nice to see the steps to do the work(the logic). Which tool you recommend to do the work? UML or BPM?

[@QA1]

@Higinio Fuentes - Thank you for my channel's first comment of the year! UML (Unified Modeling Language) deals with objects while BPM (Business Process Management) deals with processes. Both have their advantages but I would recommend BPM because it is applicable to both the IT systems and business processes. UML is more suited to the development of IT systems. Thank you 🙏

[@tazz763]

Thank you so much..!!!

[@hareshkachhadiya3589]

graat teaching sir

[@namikmasimov2682]

Thank you for this video, it is very useful. Hello from Baku.

[@kumarshubhamchoudhary1885]

So helpul !! You are the Saviour.. Thanku

[@QA1]

Good to know. Thank you too.

[@reemsdahal7587]

Worth it. Thank you!

[@norad1090]

Hi,Thanks for usual support, I have a question regarding prioritizing Test cases: for example if we have 14 test cases to cover a given module and for some reasons some changes have been made and manager ask to reduce number of test cases ,is there some methods or techniques to select the TC's ?How can I select the less number of TC's with acceptable coverage. Thanks in advance.

[@QA1]

+Nora D You could combine multiple test cases using a single workflow.

[@niranalex]

Thank you.

[@QA1]

Thank you for liking this tutorial. See the other Test Design tutorials at the link,kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc

[@vishnuvamshi4645]

What is the Difference between usecase and testscenario?

[@aneelabaji]

Thanks for the information:)

[@mattbond6966]

Excellent. Thanks, very useful.

[@QA1]

You are welcome. The five test design tutorials are available at the link, kzbin.info/www/bejne/q6rHcqygprmGn9k

[@mdchowdhury5950]

thank you so much. its really helpful.

[@QA1]

Kamal chowdury Thank you, Kamal. You may find my other test design videos helpful too. They are in my Test Design playlist at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc

[@user-ht9sy4yc2e]

lovely....nice

[@rajatranjandas3308]

HI, thanks for this video. I have a query here. The query is "what is the difference between Workflow testing and Functional Testing? " Thanks for your reply in advance..

[@QA1]

Workflow testing means testing the main workflow and optional exceptional workflows in the system. Workflow testing is a kind of functional testing. I have explained how to test the different workflows (scenarios) in this video. Thank you.

[@Raouf4eva]

Hello, I was wondering as your creating test cases for all the scenarios.. how you lost out each scenario? Before creating a test case for each and how would you know you have covered all the scenarios? How would the team be apart of this in terms of reviewing it to ensure it’s in scope and etc.

[@QA1]

Hello, in this example use case, the scenarios are the main workflow and alternate workflows. Make sure that you have covered each one of them in your test cases.

[@Raouf4eva]

@@QA1 how can i develop a strategy where the team can list those scenarios before creating the test cases? Is there a situation like that?

[@QA1]

@Arty Sky - The team should cover all the workflows in the use case. Along with positive test cases, they should create the negative test cases too. They could use test design techniques to design the test data (view the videos at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc). Further, exploratory tests should supplement the test cases.

[@mango_mix9322]

So what's the difference between normal test cases n use test cases. Please reply me. Thx in advance

[@QA1]

This tutorial explains use case as a requirement format. There is no difference between "normal" test cases and test cases from the use case. Rather, normal test cases are derived from use cases (requirements). This test design technique is quite straightforward (you need to cover the normal workflow and each alternate workflow in your test cases).

[@Ottonturk]

Thanks. So i understaood that Test Case is a USE case with expected results and results and may be requirments. Am i right?

[@QA1]

Ottonturk Test case is a different documentation than a use case. One or more test cases may be derived from a single use case. The use case steps done by the actor can be used to design the test steps (in the test case). The use case steps done by the system can be used to design the expected results (in the test case). The level of detail can be different in the test case (say, more detailed test steps and test data) and the use case.Use cases are one of the inputs to write test cases. Apart from use cases, we may design test cases based on requirements in the form of software requirement specifications, design specifications, user stories, fixed bug reports, user guides and so on. Thank you for your question.

[@Ottonturk]

Software and Testing Training it's more difficult definition than i expected. Thank you for explaining: i will try to reread it tomorrow to understand deeply!

[@QA1]

Ottonturk Sorry about that. Actually, a test case is a different document than a use case. I have explained it in my video at kzbin.info/www/bejne/o5ulaouKpbagncU

[@Ottonturk]

Software and Testing Training Thank you for your time!))I will see it of cause.You made great work!

[@rajashreepatil14]

please explain primary actor and supporting actor.

[@QA1]

In the use case shown, the primary actor is the Customer (who uses the ATM system). The Bank is the supporting actor (with which the ATM system communicates).

[@rahulsonawane2587]

A use case testing can be called state Transition testing as well right?

[@QA1]

No, the reason is that a Use Case shows the functional requirements of the system as Steps. So, we need to test the main scenarios and optional scenarios of the Use Case. On the other hand, a State Transition diagram shows the system as States. So, we need to test all the valid transitions from a state to another state.

[@rahulsonawane2587]

Thanks for clarification. In my organisation I have been asked to write testing techniques on a use case via user story without actually accessing the system. So you think in this case use case testing will suffice?

[@QA1]

Your questions are welcome. It is definitely possible to write test cases without actually accessing the system. But, only use case testing would not be sufficient. You could write test cases off requirements, conversations with developers, fixed bug reports, user guides, your domain knowledge and your creativity. Please see my Test Design playlist, especially How to design Test Ideas at the link, kzbin.info/www/bejne/oKarf62lh7Off7M

[@thembakazihlotywa3458]

Hi there i need your help Chapter 4 is a problem for me the questioning is difficult please help

[@QA1]

Hi, what is your specific question please?

[@aneelabaji]

Does the developer do the use case testing or the QA?

[@QA1]

Hi Aneela, it is the QA. Many thanks for your comments.

[@shweta2706]

use case can be consider as a requirements?

[@QA1]

+Shweta Tripathi Yes, a use case details the functional requirements or features of the system.

[@adebowaledollars1]

Who is responsible for creating the use case document?

[@QA1]

It is the product owner/ business analyst role.

[@msraoswetha8250]

Good morning sir, I am Swetha . I have one interview tomarrow.On this 1. System test - Write Selenium script for automating given scenario. So please sir.give me one example how to write that scenario. Thank you sir

[@QA1]

+msrao swetha Hi Swetha, please see my Selenium WebDriver tutorial for an example. The URL is kzbin.info/www/bejne/aITdlZt-bd10jpY

[@msraoswetha8250]

ok sir, i will see. thank you.

[@muhammadilhamelhakim6483]

like -indonesia

[@QA1]

Thank you very much.

[@hobroker]

Can you share the Word or Excel file of these test cases?

[@nataliianataliia2442]

If the step is 1$ then ok 101$, 1$. What about 99$?

[@QA1]

99$ is a valid test data. But when using Boundary Value Testing (BVA), we should, at least, test both sides of the 100$ boundary i.e. 100$ and 101$. To know more about what I mean, please view the Equivalence Partitioning and BVA tutorial at kzbin.info/www/bejne/q6rHcqygprmGn9k

[@nataliianataliia2442]

@@QA1 Thank you for your attention to the answer. As I know about BVA we should take into account the step before, the value and the step after. That’s why it is a little bit confusing for me

[@QA1]

@Nataliia Nataliia - I see. Actually, BVA is related to EP because the BVA technique depends on partitions. Let's say that there is a valid partition from 1$ to 100$ and an invalid partition from 101$ onward. Where is the boundary of these two partitions? The boundary is between 100$ and 101$, In BVA, we test on both sides of this boundary, at least i.e. test for 100$ (should pass) and 101$ (should fail). 99$ (should pass) is not a boundary value but we may test it anyway. I have explained such concepts with multiple examples in the tutorial whose link I gave is in my previous comment. Thank you.

[@nataliianataliia2442]

@@QA1 ok, thank you!

[@saeedalrazi8726]

thank you sir

[@QA1]

You are welcome. I enjoyed writing the use case test cases for normal workflow, every alternate workflow and the business rule :)