Quality is delighting customers
1)You should know the basics very well
2)Should be able to understand the requirements and from that identify test scenarios and test scripts.
3)Should be able to find negative scenarios.
These are the basics things i told you for Fresher Level.
i m also fresher for the testing field. i m testing the e-commerce website.
For website testing manually how we have to write test scenarios and test scripts.
Learn the basics of software Testing ... Would recommend you to read a Book named "Foundation of Software Testing " by Rex Black.... If you dont have this book then You can drop me a mail at email@example.com with Subject line "Rex Black - Foundation "....
Okay Coming down to the query : ----
See , before writing a test scenario , you need to understand that a what is a "Test Scenario"...
and Test Cases ( Manual ) and Test Scripts ( Automated ) are always derived from the Test Scenarios....
For Now I can just tell you that a test scenario is nothing but a test condition which can be tested... Now in case of E-Commerce Website I am giving you and Example:-----------
Lets take an example of "Add Product to Cart" and "Continue Shopping " ..........
1) Test Scenario 1: - Ensure that the user is able to add a product to the Card"
Now you will write the test cases for the same .........
2) Test Scenario 2: - Ensure that once a Product has been added to the Cart , a Button appears named "Continue shopping" and Clicking on it allows the User to "Continue the further shopping"..
Now you will write test cases for the same ..........
Hope it will give a new direction to your thought ...........
Manual testing is done by software quality analysts. Who carefully analyse it by the application screens and try out different usage and input combinations.
They analyse the results to the expected delivery and report their observations. But, these manual processes have to be repeated often during the software life cycle due to either an unexpected source code change or due to other circumstances.
Some of the other factors include multiple operating conditions or hardware configurations that might appear from time to time.
Though the QA groups perform them accurately yet, the delivered software always has bugs. QA engineers always try to catch them up before the product is delivered but flaws always creep in, even though the best manual methods are followed.
Therefore, the next solution lies in the enterprises to take up or adopt test automation services which is the best way to increase the effectiveness, efficiency, and coverage to make sure quality deliverables.
Don't worry. You will learn and it's not going to take too much of your time. What you are doing the way you are doing just give your 100%.. In every step of testing you will learn new things. You can also use cloud-based platforms like LambdaTest for testing an e-commerce website. It provides you over 1400+ browsers and OS to test on.
Hi as per quality assurance services please find below the basic requirements of manual testing :
Manual Testing is basically a process of finding out the defects in any application , so here findings out the defects one should be clear about the requirements of particular application . In this type of testing the application is tested as a end user. For a manual tester he/she should be very clear about the requirements of the application which is going to be tested and after getting the requirements these are being compared when application is given to a tester. Here the role of a manual tester is find out that every single module/area , functionality and UI is working fine. Below is the simple flow which is being followed by testing a application :
- Going through the stories and gather the information.
- Creating the test cases which includes negative as well as positive scenarios.
- Execute the same on different browsers , PDA's.
- Re-verify the important areas after getting new code to check previous functionality is working fine.
- Report functional as well as UI defects.
Manual Testing is a process of finding out the defects or bugs in a software program. In this method the tester plays an important role of end user and verifies that all the features of the application are working correctly.