Printable View
Hi friends,
Really true question.
How many of you have written the step to reproduce a bug which you got from the server? I mean when open user use a website and get some server error, server make a log of this error and send a mail to admin, if this mail is forwarded to you, can you write the step? and how many of you have done it?
If the question is not clear to any of you, you may ask to me.
Ya recently i have reported a bug.
Opera has released a web browser for mobile phone.
Version 4.1 which is still in beta stage.
They have claimed that using new version of webbrowsed we can attach files from mobile phone when i tried it .it has a bug.
Whenever i attached a file of any type,instead of original file the web browsed is attaching html file of 1 kb.
To report any bug they has give option for bug reporting.
I have reported this bug using this bug reporting tool.
With steps to reproduce the bug.
The website is operamini.com
thanks and regards
trainee tester
[QUOTE=trainee_tester;29101]Ya recently i have reported a bug.
Opera has released a web browser for mobile phone.
Version 4.1 which is still in beta stage.
They have claimed that using new version of webbrowsed we can attach files from mobile phone when i tried it .it has a bug.
Whenever i attached a file of any type,instead of original file the web browsed is attaching html file of 1 kb.
To report any bug they has give option for bug reporting.
I have reported this bug using this bug reporting tool.
With steps to reproduce the bug.
The website is operamini.com
thanks and regards
trainee tester[/QUOTE]
Friend,
What so ever you have replied, comes user beta testing when user reports the bugs.
My question was for professional testers when they are working on a web project, user get the server error, but don't report it.
In this case also, we get a server mail, but we have no steps to reproduce, we have to write them.
As per my knowledge, rarely any tester do this, that's what i want to confirm, because I am doing it.
hi
can u reply me for this question u asked....regards Harri
I am not getting you harri.
I have explained the answer in my question it self, now it's like a survey question, that how many testers are doing it, or have done it?
[QUOTE=jainbrijesh;29113]Friend,
What so ever you have replied, comes user beta testing when user reports the bugs.
My question was for professional testers when they are working on a web project, user get the server error, but don't report it.
In this case also, we get a server mail, but we have no steps to reproduce, we have to write them.
As per my knowledge, rarely any tester do this, that's what i want to confirm, because I am doing it.[/QUOTE]
Hi,
If i understood you correctly, you are referring to the logs which usually are stored somewhere in the logs directory of your server.
Basicaaly the steps to reproduce will not be present in the log file, but you can always get the root cause of the failure with the help og these log files.
Hence attaching these log reports iwith your bug report will be of lots of help.
Thanks
Sabarish S
nice answer.
But only log file is not sufficient to reproduce the bug. It is just like a help, but not a proper solution. That's why tester needs to write step.
i did not get that oppurtunity to write the steps for the logs..and logs will be very technical
yes, i had written complete steps to recreate
This procedure of writing TCs out of the mails from the server is a common process as far as I know. I have done that quite a few times. Mostly such TCs were categorized as Regression tests.
But I have a question. I want to understand from jainbrijesh, what is this survey aiming at. :confused:
Hi sutnarcha,
This survey aims only that is it comes under testing to write test cases from server log/mails or not.
I think it is not the testing part, but we can generally adds it in testing. I just want to see whether it is common practice or in some companies only.
Hi Brijesh Jain,
Its totally depends on what type of testing you are doing. If you are working on Functional Testing you should always concentrate on Application Functional Flow. I mean you should see how end-user's can complete one end-to-end transaction.
But it is really required one who are working on System testing ( early testing before depolyed into FAT environments ). System testing test cases should cover end-to-end as well as each service events behaviour.
So it is really useful if someone follow Brijesh Jain's ideas to incorporate the steps in test cases.
Please someone correct If I am wrong.
Thanks
Hi all,
It is very important for a tester to reproduce a bug, for that tester need to write all the steps along with all the settings which will helpful to the devlapor to fix, ex. if one is doing the functional testings it is better he should provied his test procedure steps and observation and all.prm file.
Hi all have written the step to reproduce a bug which you got from the server? Its hard to replicate how ever depends on the particular functionality. So we take screen shots and do a regression and in the bug tracking tool assigned it as not replicable.
Hi
To me this question is not clear,can you break it into small pieces then i will collect it.
Ntwana
Hi,
ocassionally we will face this situ in UAT .. and simple we will add the tc and for steps will be formed from the log we recieved..
but intially we cant go 4 these type of tc s....
Regards.
KVM
B Simple B Sample--------------
[QUOTE=jainbrijesh;28677]Hi friends,
Really true question.
How many of you have written the step to reproduce a bug which you got from the server? I mean when open user use a website and get some server error, server make a log of this error and send a mail to admin, if this mail is forwarded to you, can you write the step? and how many of you have done it?
If the question is not clear to any of you, you may ask to me.[/QUOTE]
Hi Jain,,
Its really a nice qn...Becoz Juniors like me can hav get knowledge through ur experience,,Thanx a lot,,can u explain elaborately how to reproduce tht knida bug???tht ll be more helpful...plz do post tht...
[QUOTE=RanjeetaRajendran;35823]Hi Jain,,
Its really a nice qn...Becoz Juniors like me can hav get knowledge through ur experience,,Thanx a lot,,can u explain elaborately how to reproduce tht knida bug???tht ll be more helpful...plz do post tht...[/QUOTE]
Hi,
It all depends on your error guessing. More you will learn it with your real experience.
hi all,
i'm not able to understand the question fully.
can some one help me out?
i will give mycomments below
In my Exp i got several times "Server Error " and i logged a bug for the same
In my opinion nobody can't give the Exact repro steps for this because it is consistent and you may get in different scenarios.
Even you get mail from admin regarding the log details also you may not be able to identify the root cause for that in manty cases.
i feel For developers also its challenging thing some times to find the root cause
Can some one validate my ans and correct me if any thing wrong?
im the fresher in testing. will i get jobs in this recession
[QUOTE=krisn;46463]im the fresher in testing. will i get jobs in this recession[/QUOTE]
hai krishn,
Just register in job sites companies started recruiting now. So please upload your resume in job sites.
Thanks
Deepa
I have written the test cases for the same.
Infact it was the part of requiurement i.e exception handling requirement.
Its very difficult to write test cases, but we can do so with help of BA & administrators
Thanks
Amit Mhatre
Automation tools and istqb training in bangaloreother - richmond town - institute/schoolposted on: thu, 17 sep 2009, 11:10 am share ► retweetpowersoft technologies, with its commitment to software testing training industry, is designed to provide a comprehensive education environment to individuals and enterprises, offering training, and certifications in the identified area of software testing, which is customized to the varied needs of audiences with diverse backgrounds at individual, project and organization level. We welcome each one of you to our 'campus', where latest technology, innovative teaching methodologies and quality education are blended together to create unique learning experiences. Our vision software testing is emerging as one of the driving segments in the it industry in india as well as across the globe. Our vision is to create a campus where anyone is able to learn various aspects of software testing to find a foothold in it industry or to enhance their career. Courses offered powersoft technologies provides training on a wide selection of specialized courses. Developed and taught by industry professionals, all courses are based on the latest industry practices and are updated regularly to reflect ever changing technologies, and trends. Manual testing: this training course provides a comprehensive overview of methods and techniques that can be applied to the testing software systems. In addition the course will focus on management and documentation and team skills that ensure that testing is conducted effectively and efficiently. The course is focused on practical approaches to testing, based on the experience of the presenter. Automation: the course provides an introduction to testing tools and test automation adopting a practical orientated approach to take you through different realms of software testing & automation. The course gives the knowledge that is necessary to avoid pitfalls of test automation. We cover the following tools 1. Qtp 2. Load runner 3. Win runner 4. Test director/quality center certification: • istqb foundation certification the istqb is responsible for the international qualification scheme called "istqb certified tester this course is based on the curriculum of the "istqb certified tester, foundation level", which covers tasks, methods and techniques of software testing, testing process, test policy and handbook, test plan and test control, test deviation management, risk based test management, test metrics and test staff qualification skills. Benefits from us • availability of system for unlimited practice • affordable prices and easy installments • personal attention to everyone. • placement assistance after the training • real time consultants with practical knowledge in respective area classes are conducted on weekdays and weekend with flexible timings. We also provide online training. Other courses offered by us sas, php, other web technologies for further information contact – corporate office (india) contact person: luna #5/1, rich buildings, suite 3b, richmond road, bangalore-560025 land line no. – 080-41226001 mobile no. - 9620540885
Hi,
According to me when we find any server error then in step to reproduce we should attach the log details and mail contents which you get from the admin. And we should also try to reporduce same steps for the bug. please correct me if anything wrong.
Hi Jainbrijesh,
This is one of the practices followed in writing test cases in Graybox testing. Mostly seen while testing the embedded s/w, testing any services in the telecom domain, sql injection while performing the database testing in some areas.
Some times while following the normal flow of testing we see some strange error coming up. So we refer to the logs and then create the steps to replicate the bugs. The test cases created in thse scenarios will be added to the regression test cases and tested once the patches are received.
So far I have not seen any standard approach for performing the Graybox testing techniques anywhere. Sometimes we end up redoing the Graybox testing after we complete the blackbox testing techniques just to see if we were left with any areas uncovered and the logs had captured, especially while testing the services.
Hi,
If you have such case, where you are getting an error at the server end and that is reported to you through a automated mailer, then you need to drill down the cause of error by using the information you have in the mail. You can use the server log and other evidence and try to under stand what have been the cause of this error and try to re-produce it in your environment.
Once you have reproduce the error then it will become easier for you to write the steps for the same.
Remember if you can re-produce any bug then only you can expect it to be fixed.
Hope this will help you to understand the approach you should adopt to test such kind of error.
What i believe, you can troubleshoot any issue by tracing the error log, but can not write test case based on that.
To write test case you need appropriate repro-steps and if that is not given, it become hard for developer to re-pro that bug. But in your case you have received the error log file, which was generated due to some malfunctioning of the system which is unknown.However you can include it to your test cases for future reference, once you got the solution and the root cause of the issue reported.
Sorry sir i'm a fresher..I cant able to ans this question..Can u reply me ans for this question...
regards vino..