Test case doesn’t include actual result, only expected result. If the test case fails, then should be created a bug report with expected and actual result. And we have link this bug report to the respective test case.
hello sir, hope you're fine. i have a question about writing test cases. when we want to write different test cases for a specific scenarios, we should think of both negative and positive cases like for example login test cases( we should test with both valid ans invalid data). My question is: is this valable for all scenarios? for example, if i would like to write test cases for testing a buttom, what are the negatif test cases? for me, the only test case possible is to test if the buttom work correctly, i mean if the buttom open the right page. could you please help me about this?
I don't think there will have negative test cases as well. All you need to test is - (including the one you mentioned) testing by using different browsers and devices. secondly, testing by clicking on the button repetitively and observing the behavior. Also, testing by clicking back and forth. However, a negative test case might be clicking outside the button and observing whether it works
@@mathijsvandam1965 If you have a complex GUI with business logic specific items and functionality. It would take a very long time to describe the necessary steps (if even possible) in a way that any user can execute them. Moreover the user should not blindly click on things without knowing what she/he is actually doing.
Your explanation is clear . Thank you.We need more videos on software testing .
Thank you for this! I'm just getting started in QA and this has simplified a lot of unknowns for me. Well done!
Such a concise explanation. Thank you!
Thank you for all your videos.
They are so well explained.
Thank you brother. It is very clear to understand❤❤❤
I really like the explanation. So concise
Test case doesn’t include actual result, only expected result. If the test case fails, then should be created a bug report with expected and actual result. And we have link this bug report to the respective test case.
no
it is really helpful to me..
good content.
Good explanation! Thank you very helpfull
Thanks, enjoy!
very good explanation. Thanks
Perfect Video!
Great job👏🏻👏🏻👏🏻
Structured and refined info✊👏🏻🐝📯🥃
We're glad to receive such feedback! Thanks, Igor. 💜
Super helpful!
Very clear. Thanks.
Excellent video
Good explanation! Thank you very helpful
hello sir, hope you're fine. i have a question about writing test cases. when we want to write different test cases for a specific scenarios, we should think of both negative and positive cases like for example login test cases( we should test with both valid ans invalid data). My question is: is this valable for all scenarios? for example, if i would like to write test cases for testing a buttom, what are the negatif test cases?
for me, the only test case possible is to test if the buttom work correctly, i mean if the buttom open the right page. could you please help me about this?
I don't think there will have negative test cases as well. All you need to test is - (including the one you mentioned) testing by using different browsers and devices. secondly, testing by clicking on the button repetitively and observing the behavior. Also, testing by clicking back and forth. However, a negative test case might be clicking outside the button and observing whether it works
Amazing video! Thanks a lot!
thanks a lot
Wonderful
thanks good explanation
Thanks for your feedback, Wesam!
niceee! thankyou
thank youu good work
Thanks, Dulitha! Check our Knowledge Base for more useful insights: www.qamadness.com/knowledge-base/. 🙂
thank you
thank 🙏🙏🙏
Thanks
Thank u
Concise
🔥
👍👍👍 ☕
I don't think that it is always possible to create test cases in a way that someone using software for the first time understands them.
I don't agree, can you give me an example in which you think it wont be possible?
@@mathijsvandam1965 If you have a complex GUI with business logic specific items and functionality. It would take a very long time to describe the necessary steps (if even possible) in a way that any user can execute them. Moreover the user should not blindly click on things without knowing what she/he is actually doing.
ohh some one with siple explanation
Thank u