Software Testing Tutorials (full set): kzread.info/head/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM

Excellent. Very SIMPLE, easy to understand with A LOT of information. Thank you for posting this. I will check your other ones

Thank you very much.You’re a genius.

Really effective video easy to understand and easy to learn. Thnx forgiving better idea for writing test cases

This is a very different test case I have seen so far...very nice 👌

Thank you very much! This is also very helpful for a Game Designer like me! :)

I have always think writing test cases takes me a lot of time. You gave a more effective way to write them. It is really a sample, easy way to write and understand. Good job!!

@myfashionstore1

2 жыл бұрын

Kindly visit below mentioned link kzread.info/dash/bejne/q5mFpsOPl5Dfo7w.html

thanks for writing test cases in this manner. easily understable. thanks once again

Hello Inder, I have finished my software tester course about a year ago. I am now in the market & I watched your videos. You are simply great. The way tou explain with all the details is so good. I have watched lot of videos on KZread, but you are the best. Thank you for doing this for the people. Keep it up and best of luck. Shahid,VA

@QA1

9 жыл бұрын

Hello Shahid, I am very glad that you liked my videos. Appreciate your comment. Best regards, Inder.

this is really good video. Very easy to understand.

Thank you so much! This helped me ^^

here is another on of your good effort. Great JOB Man!!

@QA1

9 жыл бұрын

Mhilu, many thanks for your support. Inder.

Excellent video!

Wow this, thank you very much to this video. Writing test cases was really a hustle.

i like this short cut..great job!!!!1

very clear to understand..

Excellent Sir 🙏

Thanks Inderji.

You sir, are amazing. thank you very much for the clear practical teaching.

@QA1

6 жыл бұрын

Dikole, glad that you liked it. Best wishes, Inder

Thank you sir ..........

Thank you very much!

This is so interesting... Thanks for useful information

Cheers Champion

Really great,very useful

Good approach.

very good... a have learnt a lot

Amazing! Though I have done testing course, I found this video a wonderful lesson.. kudos to the teacher..

@myfashionstore1

2 жыл бұрын

Kindly visit below mentioned link kzread.info/dash/bejne/q5mFpsOPl5Dfo7w.html

Very helpful. Thank you so much

thank you for sharing that with us ! it is very helpful (Y)

Thank you sir. Awesome video. I am gonna implement those thing

Very understandable, Thanks.

Very Brilliant

You made testing really easy! short but very effective video

@QA1

9 жыл бұрын

Many thanks, Kanchan. Glad that you liked this video.

nice video sir. can u please explain loan life cycle in terms of testing ..this the interview question ask by interviewr

Great Video!!! Do you have videos for QTP also, if so pls share it

Thanks for the valuable information..If you can explain for different other functions ( other than login functionality ) it will be much more useful

@QA1

9 жыл бұрын

Thank you for your comment. Here are a couple of my video where I have shown how to test other functionality: - How to test a web app at kzread.info/dash/bejne/nX6r0quMacTWpbw.html - How to test reports at kzread.info/dash/bejne/YnyCmKmhZ9zTZto.html Hope you like these :)

I will shortly be starting my software testing course and I found your video to be very useful and would like to know more about SRS document for testing.

@QA1

9 жыл бұрын

I have explained the different requirements formats in my video, How to review Software Requirements at kzread.info/dash/bejne/iK5rtrNslaS3mbg.html In the video, you can see the URL for a sample SRS document. Thank you.

Simple and effective steps..... Thank you Sir

@QA1

9 жыл бұрын

rambabuu1 Glad to help. Thank you for your comment.

Really helpful how to write effective test cases in short time, need some more basic test case procedure for beginners

Super cool, thanks

Thank you for the clear examples! And I think about of the place where we give valid and invalid values of inputs. Can we add Test data column before Steps one? Do you have more videos with test cases examples?

@QA1

Жыл бұрын

@Nataliia Nataliia - You are very welcome to ask any queries! Sure, a separate column to put Test data is more readable than writing the test data within the Steps. I do have more videos with test cases examples: 1) How to Test Software Manually (test cases of a web application) - kzread.info/dash/bejne/nX6r0quMacTWpbw.html Test Automation cases explained in kzread.info/dash/bejne/n45ltdtuetisp6w.html 2) Test Cases in Manual Testing - kzread.info/dash/bejne/n552m7qNoLTTl8Y.html 3) Use Case Testing - kzread.info/dash/bejne/em1ptLpuqqmyk6Q.html I think that you have already viewed the use case but I have explained the test cases in that video from 9:32 Thank you.

This is the best video I have come across, Well defined and explained. Well done sir, great work! Hugs!! Do you have videos of manual testing using java? Regards

@QA1

10 жыл бұрын

Hi Hayley, there are many manual testing videos in our playlist called Manual Testing. It is available at kzread.info/head/PLc3SzDYhhiGWADEQx4GIITh_O8jyVWu_l The concepts of testing covered in these videos are the same for different types of applications. Like Java applications, websites, desktop applications and so on. I hope that I understood your question correctly. Thanks for your comment.

Excellent sir .

Thank you. Very good video :simple and efficient.

@QA1

10 жыл бұрын

You are welcome, Privet :) Appreciate your comment.

Great video viewed from Botswana. liked, and will also join the linkedin group... gr8.

@QA1

8 жыл бұрын

Stroke Hope that you like the other videos too in my playlist, Manual Testing Tutorials. Thank you for your support.

thank you very much it will useful a lot

Thank you so much, You can only read so much online. But to actually see it in action is very good!

@QA1

10 жыл бұрын

Thank you for your comment.

Thanks.. Good video with clear explanation..!

@QA1

10 жыл бұрын

Mayur, thank you for your comment. The link to subscribe to this channel is kzread.info

great video!! anyone can fall in love with testing after watching this .. At least, I am. Could you please guide me how to prepare questions on Manual testing Interview questions. I am always stuck in the interview on manual testing questions (i was asked that how will you write test cases for mobile, what do you do in non-functional testing, what will be my approach to test (as a junior tester), what will you do before starting testing? ) I was asked these questions in last 3 interviews. i think my concepts of manual testing are very poor. please help me.i read your videos on Test plan and test strategy but its for the Team lead.

@QA1

5 жыл бұрын

Hi Sandy, many thanks for your comments. Regarding the interview questions: 1) for How to write test cases for anything, please view my tutorial on Test Ideas at the link, kzread.info/dash/bejne/nKl8sNyogrHSebQ.html 2) for what do you do in non-functional testing like performance testing, see first 40 minutes of my JMeter tutorial at the link, kzread.info/dash/bejne/ZqGaqLWrqNPSYLw.html 3) for approach to test (and many other things), see my video on Software Tester job role at the link, kzread.info/dash/bejne/nmlnmdaJm8vKfqw.html Please let me know if I missed anything.

Very good training...Thank You for your effort in making a good tutorial video.

@QA1

9 жыл бұрын

Bindu Patel Many thanks for your support and comment.

@rajatgodbole6938

2 жыл бұрын

Didi aap testing me job krti ho

Hi, Thank you for this great video, Is there difference between writing test case for different type of testing (ex: system testing or unit testing)? or we use the same test cases

@QA1

8 жыл бұрын

Nora D Thank you for your question. I assume that you are referring to the test case formats for unit testing or system testing. These formats may be the same or different depending on the needs of the project, team or organization.

it helps a lot. thank you so much for sharing...

@QA1

2 жыл бұрын

@Pyae Pyae Moe Aung - thank you for your comment. View the full playlist at kzread.info/head/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM

Thanks for uploading this video, it is really helpful for beginners

@QA1

10 жыл бұрын

Thank you, Suresh. The concept is "don't repeat yourself" and it is applicable elsewhere such as in programming and documentation.

Thanks! Very informative

@QA1

10 жыл бұрын

Andrew, thanks a lot.

superb video

@QA1

10 жыл бұрын

Jyoti, many thanks. Check out the exciting upcoming videos too.

@sundariMamulu

10 жыл бұрын

okay thank you

Nice, v cover all probabilities with little effort.

amazing explanation

Thank you. Very helpful.

@QA1

9 жыл бұрын

Rakesh AI Rakesh, many thanks for your comment.

Hi, Mr. Singh, very good video. I really like it. I am a newbie in testing and I am slowly learning testing from online. Please upload some QA Manual Testing Videos for newbies. thanks

@QA1

10 жыл бұрын

Thank you, Payal. There are many videos in my playlist, Manual Testing. I will upload a number of more videos so please subscribe to know about the same. Thanks again.

thanks for your effort,appreciate.

@QA1

10 жыл бұрын

Bilal, thank you.

thanks for the information

@QA1

Жыл бұрын

Always welcome

awesome video sir please upload more videos regarding manual testing with new tricks

@QA1

10 жыл бұрын

Rakesh, thank you :)

Thanks a lot.. Its very clear explanation video for beginners... Keep posting like this Videos sir...

@QA1

10 жыл бұрын

Sirisha, you are very welcome. Check out our playlist, Manual Testing Tutorials. It has many useful videos for beginners.

Thanks you, teacher. You made my day, you've made an awesome lesson!!! I'm going to have a Tester Interview tomorrow. I'll apply what I learn from you for that. Thanks again!

REALLY HELPFUL, Thanks a lot

@QA1

10 жыл бұрын

Taslima, many thanks. Please let me know your needed topic so that I can consider uploading videos on those.

very useful and refreshing clear example. Thank you. Do you have videos on automation testing and or NFT?

@QA1

9 жыл бұрын

lidiaabraham Many thanks for your comment. Yes, I do have several test automation videos at kzread.info/head/PLc3SzDYhhiGXVcy8EcrTSfwsC-v8EUZvg

nice explanation

very good approach

Very inspiring video Can we expect more videos from u related

@QA1

6 жыл бұрын

Many thanks, Mitthansh. Yes, I will upload more related videos but please view my playlist of 37 video tutorials at the link, kzread.info/head/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM

great tutorial well explained and what an engaging voice. Well done Inder.

@QA1

9 жыл бұрын

gulelva1 Thank you for your support. Best regards, Inder

Thank you brother for sharing your learning skills ᥬ🤗᭄

@myfashionstore1

2 жыл бұрын

Kindly visit below mentioned link kzread.info/dash/bejne/q5mFpsOPl5Dfo7w.html

Thank you, good videos.

@QA1

9 жыл бұрын

George Vernon Many thanks, appreciate your comment.

Very nice tutorials specially the combination part you told

@QA1

9 жыл бұрын

ritika ritu Thank you. You may like my video on Decision Tables in which I have explained the combinations in multiple examples. The link is kzread.info/dash/bejne/d3hmy6yRm8fOc7Q.html

Its very helpful those who r fresher's to learning testcase

@QA1

9 жыл бұрын

meerambi palagiri Thanks, Meerambi.

Hi Thank you again for your useful information,from your point of view what is the topics /outline for new tester (fresher) groining Agile testing department.Thanks in advance.

@QA1

8 жыл бұрын

Nora D Thank you for your question. If I understood it correctly, the new tester should be familiar with the industry domain, the clients, the existing system, the team and the project/ test management system, the agile process and the environments in which the system runs.

thanks..... nice and simple to understand.

@QA1

10 жыл бұрын

Dinesh, thank you :)

Its easy understandable .Thanks

Good work Inder!!!

@QA1

9 жыл бұрын

Amit - thank you very much.

Hi Inder, You have some interesting test information posted here, really liked it. Even at this basic stage i thought it would still be good to add the location of the test (like webpage in web apps) coz the same test can have diff expected results depending on the location of test. What's your take?

@QA1

9 жыл бұрын

Aruna Nandakumar Hi Aruna, Yes, we can include the test data which is not obvious to the tester. Such as the URL, valid username and password pair, error message and the home page layout and data.

Wonderful singh... it helps in real time.. thank you also please tell us more about how to write test cases for web application like airline ticketing......

@QA1

9 жыл бұрын

Thank you for your suggestion. This topic is on my to-do list. Inder.

wonderful Inder Singh.

@QA1

9 жыл бұрын

Many thanks, Adam. Appreciate your comment :)

first time am learning course so ...nice explanation ...singh

@QA1

9 жыл бұрын

Thank you :)

Thanks m8

very good for non IT learners. thanks

@QA1

9 жыл бұрын

Appreciate your comment. Thank you.

easy to understand sir ....thank you

@QA1

9 жыл бұрын

Sahil Kakkar Thank you too.

Good video that covers a lot of the basics. I strongly suggest to not use "should" when describing expected results. It is unclear wording as it suggests that it might be OK when the result does not occur. Further, be far more specific when it comes to inputs. As a tester, how do I know what constitutes a valid or invalid user name? I understand it is an example, but using such vague language in test cases leaves a lot up for interpretation. Test case 2 lacks detail as to which error message is to be expected. One good option for cutting down on test case creation time is writing generic test cases that need minimal editing for each test scenario. Keep those generic tests in a easily accessible library. Copying and pasting followed by some editing is not only fast and easy, but it also adds consistency to tests. Keep a reference in place so that finding all similar tests is easy in case all of them need to be changed. Some other things to consider and outside of what the video is about: Using a spreadsheet is simple means to document test cases, but it makes linking test cases to changesets, work items, and bug reports difficult. Use a test case management system instead. Also include any security related tests as test cases, at least SQL/HTML/JS injection.

@QA1

6 жыл бұрын

Hi Ramon, I agree that "should" can be replaced with a stronger word, like "must". And yes, we can either mention the test data (valid username and password pair) or refer the procedure to create this test data. But, I don't agree with copy and paste followed by editing because it sounds like a waste of time. Why not just document only the ~differences~ from the generic test? What do you think about adding other tests like performance tests or accessibility tests?

@ramonsequoia8586

6 жыл бұрын

I use Microsoft Test Manager as tool and cloning a test case takes a second and moving it to the desired spot another second. The items needing editing are clearly marked and replacing them takes a few seconds per test. It will take more time to document the differences in a way that anyone within the team or from the outside (we often get help from other departments) can run the test with ease. When executing the tests we do not want the tester to spend time on thinking about what the test steps are. Their focus needs to be on testing what is in the test case and what happens left and right from the designated path. Using a test case library cut down on test case creation time a lot. In many cases I copy tests from other test suites where I know I do not have to edit anything. Copy and paste is always faster and more consistent than reinventing the wheel. A clear yes on performance tests. We run tests using at least twice the amount of records that we know the largest system includes, but stop there. There is little point in spending a lot of time optimizing for performance using a number of records users will never encounter. In case we were wrong we can still make adjustments. Performance tests also include single record performance. Accessibility tests is a vague term. We do UX tests as in "How many clicks does it need to do X?" during exploratory testing. As far as accessibility for screen readers and such we have tests using the Nu validator.

@QA1

6 жыл бұрын

Thank you. Even if it takes a couple of seconds, I don't like copying and pasting the tests. If the original changes, then who knows how many test cases (and where) have to be updated? There is more clarity on Accessibility testing these days. For example, there are Web Content Accessibility Guidelines. aria-controls MUST be present in the web elements.

@ramonsequoia8586

6 жыл бұрын

That is where test case management systems come in. The test cases are referenced back to the source test case and updating all of them requires writing a simple query (takes a minute) and then replicating any changes in each of the copies. This never takes more than a few hours even for often reused cases. We do have several tests that are indeed generic and get simply added to test suites. Changing those is even easier, change the source and all instances of the test case are changed at the same time. Anything other than copy and paste will take more time, be much harder to maintain, and lack consistency. Can't really do that well with spreadsheets. Using Excel or Calc is the last resort when the budget is 0. Even then, there are several free test case management tools available.

@denisabaicu3652

Жыл бұрын

@@ramonsequoia8586 Hello! Can you tell me what are those free test case management tools? Thank you!

Thank you so much sir.. if possible upload some videos related to this concept, that will help me a lot.. I am very week to write test case please help me.or If you can recommend any test case book so i can improve my writing test case skill.

easy to understand good one thank u

@QA1

9 жыл бұрын

Jyothi Rmayi Hi Jyothi, many thanks for your support.

Thank you Sir

Thank You Inder.Can you just upload a video on how to write a test case for a website.

Thank you.. Im new to testing..

@QA1

9 жыл бұрын

swollen4ever You are welcome. Please find the complete list of my basic software testing tutorials at kzread.info/head/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM

Hii, sir i never seen before like this much clear and usefull video for beginners thank u so much sir

@QA1

10 жыл бұрын

Thank you. Please also view the videos in this channel's playlist, Manual Testing Tutorials for a systematic collection of testing videos for beginners.

Thank you sir...its very usefull one...

@QA1

10 жыл бұрын

You are welcome :)

It really helpful and good work.....

@QA1

9 жыл бұрын

Charitha, thank you.

really good work and helps us a lot....

@QA1

9 жыл бұрын

Many thanks for sharing your comment.

Good attempt for Testing community~~Sivakumar

@QA1

9 жыл бұрын

Sivakumar - many thanks for your comment. Please consider to subscribe for the latest training videos. Thank you. Inder

hi, sir thank you very much for providing these videos, it help's a lot to me. Is this quick to write test cases can we write in real -time applications???

@QA1

8 жыл бұрын

+Sahithi Kolisetti Yes, if there is consensus among the stakeholders for the same. And there is no requirement that mandates another test case format.

Great Videos..

@QA1

9 жыл бұрын

Praveen, thank you for your comment. Inder.

thank you sir!

@QA1

6 жыл бұрын

Ron, many thanks. Check out all my software testing tutorials at kzread.info/head/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM

Hi, Thanks for your replay. Not only the format, either the content should it be different based on the testing type ,or the test cases should be the same for all types. and based on that ,during the testing preparation the team should create test cases based on the planed test type.

@QA1

8 жыл бұрын

Nora D Hi there. Of course, the content will be different for test cases for different levels, unit testing, integration testing, system testing and acceptance testing. For example, in unit test cases, you may want to test particular methods. In integration test cases, you may want to test the interactions between unit-tested components. And so on.