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
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!
@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
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....
@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 🙏
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.
Kamal chowdury Thank you, Kamal. You may find my other test design videos helpful too. They are in my Test Design playlist at ru-vid.com/group/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
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..
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.
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.
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.
@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 ru-vid.com/group/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc). Further, exploratory tests should supplement the test cases.
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).
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 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.
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!
Ottonturk Sorry about that. Actually, a test case is a different document than a use case. I have explained it in my video at ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-mjB9XTpQmgc.html
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.
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?
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, ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-juHNzoRNlIQ.html
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
+msrao swetha Hi Swetha, please see my Selenium WebDriver tutorial for an example. The URL is ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-2SzdhH8xAX4.html
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 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-uydAyjqTSiw.html
@@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
@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.
