Sometimes Tester need common sense to test a application!!!
I am saying this because most of the times it is not possible to test the whole application within the specified time. In such situations it’s better to find out the risk factors in the projects and concentrate on them.
Here are some points to be considered when you are in such a situation:
1) Find out Important functionality is your project?
2) Find out High-risk module of the project?
3) Which functionality is most visible to the user?
4) Which functionality has the largest safety impact?
5) Which functionality has the largest financial impact on users?
6) Which aspects of the application are most important to the customer?
7) Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
9) What do the developers think are the highest-risk aspects of the application?
10) What kinds of problems would cause the worst publicity?
11) What kinds of problems would cause the most customer service complaints?
12) What kinds of tests could easily cover multiple functionalities?
Considering these points you can greatly reduce the risk of project releasing under less time constraint.
Feel free to ask me any testing query, resume tips or job help.
34 comments ↓
thanks for the tips
What kinds of problems would cause the worst publicity?
i dint get it , can u tell me in brief please
hi,
can u give me a sample use case and test case.
Same as template also ok…….
I was asked in an interview, ”When do u stop testing?”
What should be a probable answer to that?
I was asked for an interview on What all types of Test Estimation models are there and to describe each one?
I was even asked What all types of Risks are there in Software Testing?
Suppose i have a project when clicking English tab, all are displayed in English- inclusive of date and currency(Eg:- dd/mm/yy and $) and When clicking French all are in French, ie date and currency becomes (Eg:- mm/dd/yy and Euro). Can you please tell me what is Localization testing and Internationalization testing in the above case?
When a project is made purely in French? Is Localization testing done there?
Can u please post me test case sample of Localisation testing , How to conduct the localisation testing?
Can you please tell me the tools which are used for Internationlization testing and risks involved.
Hi,
I have to start writing manual test cases . I am not sure if manual test cases shoul dbe written for fixed data or we should use parameterization. I would also like to know if it is a good practice to make small test cases and combine them into a test set or make end to end test cases
Hi,
If we using functional test case then we use fixed data and if necessary in concentrate unit test case then we go for parameterization.
in automation it is must to go for parameterization and data driven.
Hi ,
Thanks. Another question , how can I structure the tests so that we can re use the cases even if the form changes for eg , for a web site that does the following :
Login , collect information about a persons( personal, credit card , company , team , event , misc information),
should there be only one end to end test or many small tests for each related group of information .
Again the combination of data against the entire end to end process . how will that work ?
Thanks
Hi,
Now,Collecting information through web page is done by validation itself(BY program),so v have 2 check whether the system response correctly or not.In this case functional testing(end to end testing) is more than enough.
But, the same case login page followed by shopping page,where the same data required in that situation unit test case (individual module) should be tested.because the data has to be validate against the bank details and process him to next steps.so,we concentrate more on this page.
The same process but differ from application to application,so based on the functionality of the project v have to choose the test cases.
Question 2:
The Combination of data can be modified to use for functional test case.if u want to learn more than practice with two small application having same functions.
Hi,
In testing anything is possible.Before writing end to end or many small test cases,understand the flow of application because with minimum input v have to obtain maximum output.
Now,Collecting information through web page is done by validation itself(BY program),so v have 2 check whether the system response correctly or not.In this case functional testing(end to end testing) is more than enough.
But, the same case login page followed by shopping page,where the same data required in that situation unit test case (individual module) should be tested.because the data has to be validate against the bank details and process him to next steps.so,we concentrate more on this page.
The same process but differ from application to application,so based on the functionality of the project v have to choose the test cases.
Question 2:
The Combination of data can be modified to use for functional test case.if u want to learn more than practice with two small application having same functions.
Regards,
Raja
Too good. Thank for the tips
Thax for tip
Hi Shahanaz R,
This is Suresh Working as test Engineer i have mentioned Types of Risks as below:
1.Software Risk
2.business Risk
3.Schedule Risk
4.Teechnical Risk
5.Programatic Risk
6.budget Risk
Thanks
Suresh
bsuresh7282@gmail.com
Hi Tanvi,
I have mentioned Reasons for to stop testing as below:
1.Try continuing testing and logging the critical defects
2.all quality goals defined at the start of the project have been met.
3.After complete Alpha and Beta Testing
4.Successful use of specific test case design methodologies
5.A percentage of coverage for each coverage category
6.Rate of error detection falls below a specified threshold.
Thanks,
Suresh
bsuresh7282@gmail.com
Hi Suresh,
You have mentioned the different types of risks, would you please explain each risk. Alternatively could you suggest a book on Risk Testing .
Thanks
Hi Sonia,
I have Mentioned Types of Risks with Explanations as below:
Risk Identification
1.Software Risks – Knowledge of the most common risks associated with software development, and the platform you are working on.
2.Testing Risks – Knowledge of the most common risks associated with software testing for the platform you are working on, tools being used, and test methods being applied.
3.Premature Release Risk – Ability to determine the risk associated with releasing unsatisfactory or untested software products.
4.Business Risks – Most common risks associated with the business using the software.
5.Risk Methods – Strategies and approaches for identifying risks or problems associated with implementing and operating information technology, products, and processes; assessing their likelihood, and initiating strategies to test for those risks.
Managing Risks
6.Risk Magnitude – Ability to rank the severity of a risk categorically or quantitatively.
7.Risk Reduction Methods – The strategies and approaches that can be used to minimize the magnitude of a risk.
8.Contingency Planning – Plans to reduce the magnitude of a known risk should the risk event occur.
Thanks,
Suresh
bsuresh7282@gmail.com
Thank you for the valuable information Suresh
[...] Don’t run out of time to do high priority testing tasks. Prioritize your testing work from high to low priority and plan [...]
Hi,
The article was good. Could you pls send me some testing resume format? Also some ideas about use case…
[...] Don’t run out of time to do high priority testing tasks. Prioritize your testing work from high to low priority and plan [...]
hi…………………..i wanted to know about test cases with example
Hi Parul,
Below is the sample test case
Project Form UIN:
System Name: Module Name:
Test Sub-Module :
Tester Name Signature Date/Time
TM Rajamurugesh
Test Procedures:
Hardware: NA
Software: NA
Communications: NA
Database:
Server Configuration:
Client Configuration: NA
Test Tools/Techniques/Methodologies: Manual
Test Location:
Dev Environment : Dev URL
Test Environment : test URL
Test Cases & Reports:
SNo-Objective-Test Case- Navigation-Inputs-ExpectedOutputs-Test Result (Pass/Fail)
SNo-Objective-Test Case- Navigation-Inputs-ExpectedOutputs-Test Result (Pass/Fail)
1-aim-steps/procedure-link/event-data-what we except-pass/Fail
May i know when to stop testing? Can i get some testing resumes?
Thank you
Hi SHIVALI ,
Send me a test mail, i will reply to that mail with testing resume, test cases and some testing white papers.
My mail id:
rajamurugesh.b@gmail.com
Can you plz tell me how to prepare and clear ISTQB foundation level paper?
Hi SHivali….
When to stop testing?depends on the below:
1. When all the test cases are exected successfully
2. When the budjet allocation is over
3. When the time/scheduled for testing is met
4.When the delivery date is met to deliver the application
Can you please tell me if i can get some projects of software testing which i can do at home?
Shivali, plz read this article to get ur answer.
Use risk analysis to determine where testing should be focused.
Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
• Which functionality is most important to the project’s intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio?
Its good ..i enjoyed reading this. I will try to incorporate this in my testing….:)
Leave a Comment