Thanks for explaining in a short but clear manner, without much repetition, your videos are very clear
@QA13 ай бұрын
@shilpaagarwal8712 - Few people take the time to appreciate these videos, so many thanks for your encouraging comment! If you search Test Design Technique, you'll find my 20 videos at/ near the top of KZbin search results at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@dominicankendry4 жыл бұрын
I know this is an old video but you just got a new subscriber, nice job!
@QA14 жыл бұрын
@Kendry Jordano - Thank you. Welcome to the Software and Testing Training channel. Regards, Inder
@SimonTubesc9 жыл бұрын
17 minutes but I get two weeks worth knowledge... tnx
@dvassup7 жыл бұрын
Play it at 1.5 speed :) even faster knowledge.
@adebowaledollars14 жыл бұрын
@@dvassup so, I am not the only one who does this, I am a completely normal person.
@jimioutback4 жыл бұрын
Thank you: clear and concise explanation, and the examples were very helpful.
@QA14 жыл бұрын
@jimioutback - Glad that you liked the examples. Thank you for your comment.
@bridgetborders14527 жыл бұрын
Thank you so much! I just poured through quite a few videos and this is by far the best. Really helpful for my project.
@QA17 жыл бұрын
Bridget, great to know. You can view all my Test Design tutorials at kzbin.info/www/bejne/q6rHcqygprmGn9k
@srilakshmichirumamilla491810 жыл бұрын
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
@QA110 жыл бұрын
srilakshmi chirumamilla Yes, I do try to keep it simple and practical. Please subscribe to know about the new videos. Regards, Inder
@cherukurusable9 жыл бұрын
Hi Sir, Can i get ur email id or phone number, i would like to take Selenium training
@opalhazels429 жыл бұрын
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!
@nataliianataliia24422 жыл бұрын
Good examples and explanation. Thank you!
@QA12 жыл бұрын
@Nataliia Nataliia - You are welcome! Thank you for your comment!
@higiniofuentes25513 жыл бұрын
Thank you for this very interesting video!
@vishalprajapti89969 жыл бұрын
Excellent Video, you have done an amazing job.
@QA19 жыл бұрын
***** Thank you, Vishal. You may like my other videos in my playlist called Test Design at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@Swami98273 жыл бұрын
Thank you for exapling what is exactly use case is no one will go through deatil explanation like you
@QA13 жыл бұрын
@Shambala Swami - Thank you for your awesome comment 👍 I really appreciate it. - Inder P Singh
@vasukiani35639 жыл бұрын
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....
@TheFfgo5 жыл бұрын
clear explanation, thank you
@bandipratima4 жыл бұрын
Thank you, no confusion. clear.
@KomalYadav-di3qz4 жыл бұрын
Delivery of content is very awesome , simply explained thankyou sir
@QA14 жыл бұрын
@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
@esraashokry88665 жыл бұрын
Thank u so much....very useful😊😊
@kumarshubhamchoudhary18857 жыл бұрын
So helpul !! You are the Saviour.. Thanku
@QA17 жыл бұрын
Good to know. Thank you too.
@reemsdahal75876 жыл бұрын
Worth it. Thank you!
@Swami98273 жыл бұрын
And I think this is very very .... Helpful to me
@kaminisenthil36068 жыл бұрын
Very helpful and well phased 👍🏽
@LearnEnglishVD8 жыл бұрын
Nice tutorial. Thnx!
@louisv8210 жыл бұрын
Thank you. Very helpful :)
@malathisaravanan285 жыл бұрын
thank you sir
@namikmasimov26829 жыл бұрын
Thank you for this video, it is very useful. Hello from Baku.
@hygia15406 жыл бұрын
Nice video. Thank you
@mattbond69667 жыл бұрын
Excellent. Thanks, very useful.
@QA17 жыл бұрын
You are welcome. The five test design tutorials are available at the link, kzbin.info/www/bejne/q6rHcqygprmGn9k
@anisul-islam5 жыл бұрын
Thanks. I found this very helpful.
@QA15 жыл бұрын
Thanks. You can check out my other test design tutorials. The link is kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@higiniofuentes25513 жыл бұрын
This is nice to see the steps to do the work(the logic). Which tool you recommend to do the work? UML or BPM?
@QA13 жыл бұрын
@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 🙏
@hareshkachhadiya35898 жыл бұрын
graat teaching sir
@niranalex5 жыл бұрын
Thank you.
@QA15 жыл бұрын
Thank you for liking this tutorial. See the other Test Design tutorials at the link,kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@mdchowdhury595010 жыл бұрын
thank you so much. its really helpful.
@QA110 жыл бұрын
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
@aneelabaji6 жыл бұрын
Thanks for the information:)
@tazz76310 жыл бұрын
Thank you so much..!!!
@user-ht9sy4yc2e8 жыл бұрын
lovely....nice
@vishnuvamshi46452 жыл бұрын
What is the Difference between usecase and testscenario?
@norad10909 жыл бұрын
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.
@QA19 жыл бұрын
+Nora D You could combine multiple test cases using a single workflow.
@mango_mix93226 жыл бұрын
So what's the difference between normal test cases n use test cases. Please reply me. Thx in advance
@QA16 жыл бұрын
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).
@Raouf4eva2 жыл бұрын
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.
@QA12 жыл бұрын
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.
@Raouf4eva2 жыл бұрын
@@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?
@QA12 жыл бұрын
@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.
@rajatranjandas33088 жыл бұрын
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..
@QA18 жыл бұрын
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.
@Ottonturk10 жыл бұрын
Thanks. So i understaood that Test Case is a USE case with expected results and results and may be requirments. Am i right?
@QA110 жыл бұрын
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.
@Ottonturk10 жыл бұрын
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!
@QA110 жыл бұрын
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
@Ottonturk10 жыл бұрын
Software and Testing Training Thank you for your time!))I will see it of cause.You made great work!
@rahulsonawane25876 жыл бұрын
A use case testing can be called state Transition testing as well right?
@QA16 жыл бұрын
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.
@rahulsonawane25876 жыл бұрын
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?
@QA16 жыл бұрын
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
@shweta27068 жыл бұрын
use case can be consider as a requirements?
@QA18 жыл бұрын
+Shweta Tripathi Yes, a use case details the functional requirements or features of the system.
@aneelabaji6 жыл бұрын
Does the developer do the use case testing or the QA?
@QA16 жыл бұрын
Hi Aneela, it is the QA. Many thanks for your comments.
@rajashreepatil148 жыл бұрын
please explain primary actor and supporting actor.
@QA18 жыл бұрын
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).
@adebowaledollars14 жыл бұрын
Who is responsible for creating the use case document?
@QA14 жыл бұрын
It is the product owner/ business analyst role.
@msraoswetha82509 жыл бұрын
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
@QA19 жыл бұрын
+msrao swetha Hi Swetha, please see my Selenium WebDriver tutorial for an example. The URL is kzbin.info/www/bejne/aITdlZt-bd10jpY
@msraoswetha82509 жыл бұрын
ok sir, i will see. thank you.
@thembakazihlotywa34588 жыл бұрын
Hi there i need your help Chapter 4 is a problem for me the questioning is difficult please help
@QA18 жыл бұрын
Hi, what is your specific question please?
@muhammadilhamelhakim64834 жыл бұрын
like -indonesia
@QA14 жыл бұрын
Thank you very much.
@hobroker9 жыл бұрын
Can you share the Word or Excel file of these test cases?
@nataliianataliia24422 жыл бұрын
If the step is 1$ then ok 101$, 1$. What about 99$?
@QA12 жыл бұрын
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
@nataliianataliia24422 жыл бұрын
@@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
@QA12 жыл бұрын
@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.
@nataliianataliia24422 жыл бұрын
@@QA1 ok, thank you!
@saeedalrazi87264 жыл бұрын
thank you sir
@QA14 жыл бұрын
You are welcome. I enjoyed writing the use case test cases for normal workflow, every alternate workflow and the business rule :)