Hi

[Padmanaidu]

Hi ALL,

Am a new junior memeber of this group,am desperately looking for a job in software testing..Currently am working as junior s/w test engineer in bangalore,please provide me details where can i post my profile and opening related where in having 1 year 9months experience on the same.

Looking for a +ve reply.

Regards,
Padma

[mrudula madhuri G]

hi,
this is mrudula.can u tel me real time work in our projects?brefily explain the defect tracking tool?i have so many queries on that?pls help me?i am also trying for good job with 2y's of exp?
i am expecting +reply
thanku
mrudula G

[mrudula madhuri G]

hi,
this is mrudula.can u tel me real time work in our projects?brefily explain the defect tracking tool?i have so many queries on that?pls help me?i am also trying for good job with 2y's of exp?
i am expecting +reply
thanku
mrudula G

[Padmanaidu]

Hi Mrudula...
how r u? Its a client server application both projects...have used Quality centre test director to raise defects...currently am using excel sheet for new project...

can i know ur queries,

Regards,
Padma

hi,
this is mrudula.can u tel me real time work in our projects?brefily explain the defect tracking tool?i have so many queries on that?pls help me?i am also trying for good job with 2y's of exp?
i am expecting +reply
thanku
mrudula G

[mrudula madhuri G]

Hi Mrudula...
how r u? Its a client server application both projects...have used Quality centre test director to raise defects...currently am using excel sheet for new project...

can i know ur queries,

Regards,
Padma

HI Padma,
Thanks for ur reply.S,i have some quries on defect tracking tool.We can prepare test cases in excel sheet.But through that excel sheet how can we execute test cases.How can report the defects in defect tracking tool.In my interview they asked me how can we report the defects(asking about defect tool also).can u tel me Bug Tracking tool And Defect tracking Tool both r same?Any deference in that?give some example?plz explain brefely?
Thank You

[mrudula madhuri G]

HI Padma,
Thanks for ur reply.S,i have some quries on defect tracking tool.We can prepare test cases in excel sheet.But through that excel sheet how can we execute test cases.How can report the defects in defect tracking tool.In my interview they asked me how can we report the defects(asking about defect tool also).can u tel me Bug Tracking tool And Defect tracking Tool both r same?Any deference in that?give some example?plz explain brefely?
Thank You

[siva siva]

hiii mrudula!!

I hope below information will be useful for you..plz check it

sample bug/defect report will give you exact idea of how to report a bug in bug tracking tool??.

Here is the example scenario that caused a bug:

Lets assume in your application under test you want to create a new user with user information, for that you need to logon into the application and navigate to USERS menu > New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these information, you need to click on ‘SAVE’ button in order to save the user. Now you can see a success message saying, “New User has been created successfully”.
But when you entered into your application by logging in and navigated to USERS menu > New user, entered all the required information to create new user and clicked on SAVE button. BANG! The application crashed and you got one error page on screen. (Capture this error message window and save as a Microsoft paint file)
Now this is the bug scenario and you would like to report this as a BUG in your bug-tracking tool.

How will you report this bug effectively?

Here is the sample bug report for above mentioned example:
(Note that some ‘bug report’ fields might differ depending on your bug tracking system)

SAMPLE BUG REPORT:

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005
Description:
Application crash on clicking the SAVE button while creating a new
user, hence unable to create a new user in the application.
Steps To Reproduce:
1) Logon into the application
2) Navigate to the Users Menu > New User
3) Filled all the user information fields
4) Clicked on ‘Save’ button
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to bug..IF any)
7) And also see the attached screenshot of the error page.
Expected result: On clicking SAVE button, should be prompted to a success message “New User has been created successfully”.
(Attach ‘application crash’ screen shot.. IF any)
Save the defect/bug in the BUG TRACKING TOOL. You will get a bug id, which you can use for further bug reference.
Default ‘New bug’ mail will go to respective developer and the default module owner (Team leader or manager) for further action.

In my view Bug Tracking tool And Defect tracking Tool both are SAME..

I hope my above Information will be usefull for you heartfully,

Thanks and Regards,
SIVA

[siva siva]

hiii mrudula!!

I hope below information will be useful for you..plz check it

sample bug/defect report will give you exact idea of how to report a bug in bug tracking tool??.

Here is the example scenario that caused a bug:

Lets assume in your application under test you want to create a new user with user information, for that you need to logon into the application and navigate to USERS menu > New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these information, you need to click on ‘SAVE’ button in order to save the user. Now you can see a success message saying, “New User has been created successfully”.
But when you entered into your application by logging in and navigated to USERS menu > New user, entered all the required information to create new user and clicked on SAVE button. BANG! The application crashed and you got one error page on screen. (Capture this error message window and save as a Microsoft paint file)
Now this is the bug scenario and you would like to report this as a BUG in your bug-tracking tool.

How will you report this bug effectively?

Here is the sample bug report for above mentioned example:
(Note that some ‘bug report’ fields might differ depending on your bug tracking system)

SAMPLE BUG REPORT:

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005
Description:
Application crash on clicking the SAVE button while creating a new
user, hence unable to create a new user in the application.
Steps To Reproduce:
1) Logon into the application
2) Navigate to the Users Menu > New User
3) Filled all the user information fields
4) Clicked on ‘Save’ button
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to bug..IF any)
7) And also see the attached screenshot of the error page.
Expected result: On clicking SAVE button, should be prompted to a success message “New User has been created successfully”.
(Attach ‘application crash’ screen shot.. IF any)
Save the defect/bug in the BUG TRACKING TOOL. You will get a bug id, which you can use for further bug reference.
Default ‘New bug’ mail will go to respective developer and the default module owner (Team leader or manager) for further action.

In my view Bug Tracking tool And Defect tracking Tool both are SAME..

I hope my above Information will be usefull for you heartfully,

Thanks and Regards,
SIVA

[mrudula madhuri G]

hi siva,
Thank u so much,its very useful for me.
let me explain the testing process in both manual and QTP(Real time)
Mainly y we have to write the script for the apllication?
And when we have to run the test cases in QTP whats the process?pls tell me.
I hope u will help me
Thank U
Mrudula G

[siva siva]

MANUAL TESTING PROCESS

1) Test planning and Control:
Test planning is the activity of verifying the mission of testing, defining the objectives of testing and the specification of test activities in order to meet the objectives and mission.
It involves taking actions necessary to meet the mission and objectives of the project. In order to control testing, it should be monitored throughout the project. Feedback from monitoring and control activities of earlier testing processes will be also be used for effective Test Planning.
2) Test Analysis and Design:
Test analysis and design is the activity where general testing objectives are transformed into test conditions and test cases. Here major tasks are:
Ø Reviewing the test basis such as requirements, architecture, design, interfaces.
Ø Evaluating testability of the test.
Ø Identifying and prioritizing test conditions based on analysis of test basis.
Ø Designing and prioritizing test cases.
Ø Identifying necessary test data to support the test conditions and test cases.
Ø Designing the test environment set-up and identifying any required infrastructure and tools.
3) Test Implementation and Execution:
Test implementation and execution is the activity where test procedures or scripts are specified by combining the test cases in a particular order and including any other information needed for test execution, the environment is set up and the tests are run.
Test implementation and execution involves:
Ø Developing, implementing and prioritizing test cases.
Ø Developing and prioritizing test procedures, creating test data.
Ø Creating test suits from the test procedures for efficient test execution.
Ø Verifying that the test environment has been set up correctly.
Ø Executing test procedures either manually or by using test execution tools according to the planned sequence.
Ø Logging the outcome of the execution.
Ø Comparing actual results with expected results.
Ø Reporting bugs and analyzing them in order to establish their cause.
Ø Repeating test activities as a result of action taken for each bug. For example, re-execution of a test that previously failed in order to confirm a fix(confirmation testing), execution of tests in order to ensure that defects have not been introduced in unchanged areas of the software(regression testing).
4) Evaluating exit criteria and reporting:
Evaluating exit criteria is the activity where test execution is assessed against the defined
objectives. This should be done for each test level.

Evaluating exit criteria has the following major tasks:
Ø Checking test logs against the exit criteria specified in test planning.
Ø Assessing if more tests are needed or if the exit criteria specified should be changed.
Ø Writing a test summary report for stakeholders.
5) Test closure activities:
Test closure activities collect data from completed test activities to consolidate experience,
testware, facts and numbers. For example, when a software system is released, a test project is completed (or cancelled), a milestone has been achieved, or a maintenance release has been completed.

Test closure activities include the following major tasks:
Ø Checking which planned deliverables have been delivered.
Ø The closure of incident/bug reports.
Ø The documentation of the acceptance of the system.
Ø Finalizing and archiving testware, the test environment and the test infrastructure for later reuse.
Ø Analyzing lessons learned for future releases and projects, and the improvement of test maturity.


AUTOMATION TESTING PROCESS

1) Decision of Automation Testing:
First phase in automation is to decide if application under test can be given a nod for go ahead with automation. Usually this decision is taken by the client and test manager. Lot of factors like return on investment and future scope of the application are considered. After all calculations if return on investment seem to be positive automation of the application under test is approved.
2) Automation Test Planning:
Once the decision to automate is confirmed the next step involves on the automation plan. Here the planning team which is generally compressed of client, test manager and Automation lead decide on the automation test planning.
This plan involves decisions like how to automate, what to automate and when to automate.
3) Evaluation and Acquisition of Tool:
Once the automation plan is set up the next phase is to decide on which tool to pick up from the market. In general the evaluation team consisting of the client, test manager and automation lead together discusses and evaluates the various tools available in the market. Various factors such as cost of the tool, compatibility of the tool with the application, skilled resources required are considered to decide on the tool.
4) Design of Automation Framework:
Once the tool is decided next step is to design appropriate framework supported by the tool. Framework is generally designed by automation lead or test managers. Automation framework consists of the rules that should be followed in automation. The automation framework design defines how the scripts should be developed, integrated, executed and maintained.
5) Setup and Training of Automation Team:
Once the tool and framework is decided the next step is to select team members of the automation team. In this phase after the team is formed necessary setup (hardware and software) and training sessions are planned on application, tool and framework.
6) Development of Automation Scripts:
Once the training is over the next phase involves the automation team to start building scripts based on the training provided on tool, framework and application.
7) Review & Rework of Automation Scripts:
After developing the scripts the next phase involves reviewing the scripts. The factors that are considered while reviewing are if the scripts are following the guidelines defined in the framework. Once the review is done necessary rework is done on the scripts based on the review comments.
8) Integration of Automation Scripts:
Once the rework is completed all the scripts are integrated together for execution phase.
9) Setting up Test Execution Environment:
After integration of scripts the execution environment is set up. This setup includes setting of the number of systems, setting up of automation tool, setting up of application under test, setting up the data and environment required for execution of the scripts.
10) Execution of Automation Scripts:
In this phase, Final scripts (reviewed and reworked) are executed.
11) Analysis of Test Results:
After execution phase the result reports generated are analyzed based on the pass/fail status of the scripts.
12) Enhancement of Automation Scripts:
In this phase scripts might be modified because there might be few changed in the existing functionality of the application. Also for the new functionality added scripts are developed. Since addition and modification of scripts takes place in this stage review and rework should be done again so as shown in the figure the review and rework phase is looped back.

In Automation we are not going to write any test cases but in Manual phase it self we need to identify the Regression Test Cases, Based on Regression Suit We can prepare the Test Scripts (Based on using Tools like QTP)
For Automation testing we no need to write the test cases. In automation testing we have to write test sripts only like QTP Automation(VB scripts)

[Archana.vkk@gmail.com]

Please tell me why we do enable or disable java script and cookie in browser for web applications.
Reply me ASAP.

Thanks in advance,
Archana.