Why IBM Page Detailer?

There are five major elements that influence an end user's experience while accessing a Web site:

• The content of the page (information).

The presentation of the content (look and feel).
The efficiency of presentation (size).
• The organization of content (packaging).

• The administration of the Web site (delivery).

Although IBM Page Detailer does not address the first two elements, content and presentation, it can provide information useful in improving the last three: efficiency, organization, and administration.

Developers agree there is no absolutely "correct" way to set up a Web site. Multiple design and operational tradeoffs exist in setting up even small sites, but IBM Page Detailer can be used to quantify the impact of tradeoffs by providing performance data about the site both before and after changes. IBM Page Detailer provides information well suited to the analysis of size, packaging, and delivery elements of the end user experience. Routine use of IBM Page Detailer to analyze Web pages can also help identify new opportunities for improvement as designs are tested and moved into production.

IBM Page Detailer can also be used to help confirm Web page design standards and practices for an organization. In a test environment, proposed design standards and practices can be prototyped and analyzed with IBM Page Detailer. IBM Page Detailer can give your team insight as to what impact your new design choices will have on an end user.

The IBM Page Detailer tool is designed to explain some of the mysteries about how Web pages are delivered to Web browsers.

IBM Page Detailer can help Web developers, designers, site operators, and IT specialists to isolate problems and improve performance and user satisfaction. It does this by revealing details about the timing, size, and identity of each item in a page.The details revealed can be used to identify areas where performance could be improved to enhance the end user experience

Starting IBM Page Detailer

IBM Page Detailer attaches to the workstation TCP/IP socket stack and monitors all of the HTTP/HTTPS protocol based communications between your Web browser and the network. IBM Page Detailer then displays web activities in a series of color-coded bars.

To start IBM Page Detailer, double-click the IBM Page Detailer Basic icon:  

IBM Page Detailer Basic

This will start IBM Page Detailer.

Note:  If the icon is not on your desktop, you can find it in the IBM Page Detailer folder accessible via the Start Programs menu.

To monitor communications between your Web browser and your network, just start the browser (Internet Explorer or Netscape). Shortly after the first page has loaded into the browser, the IBM Page Detailer chart will be displayed.

Web Communications

The time it takes to download a page is the result of many factors and the interactions among them. Page designers who understand these factors can best optimize page download time. A significant factor is how basic and secured Web site communications work. ......

Automated testing that doesn’t hurt

Watir is a simple open-source library for automating web browsers. It allows you to write tests that are easy to read and easy to maintain. It is optimized for simplicity and flexibility.

Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page.

Watir is a Ruby library that works with Internet Explorer on Windows. Watir is currently being ported to support Firefox and Safari.

Like other programming languages, Ruby gives you the power to connect to databases, read data files, export XML and structure your code into reusable libraries. Unlike other programing languages, Ruby is concise and often a joy to read.

Watir stands for “Web Application Testing in Ruby”. It is pronounced water.....

for details  check http://wtr.rubyforge.org/

I run watir and given below are my  observations..

Good Points.....

1. Open source and don't have to spend penny..

2. Ruby based script and fast exection.

Drawbacks.....

1. No recording option in watir like i do in QTP or Robot

2. Coding is hard to learn and implement.

3. Very little help avilable.

Functions to be Tested & implemented in Postgis

Table of Contents

2.1. Requirements

2.2. PostGIS

2.2.1. Creating PostGIS spatially-enabled databases from an in-built template

2.2.2. Upgrading

2.2.3. Common Problems

2.3. JDBC

2.4. Loader/Dumper

PostGIS has the following requirements for building and usage:

The PostGIS module is a extension to the PostgreSQL backend server. As such, PostGIS 1.3.3SVN requires full PostgreSQL server headers access in order to compile. The PostgreSQL source code is available at http://www.postgresql.org.

PostGIS 1.3.3SVN can be built against PostgreSQL versions 7.2.0 or higher. Earlier versions of PostgreSQL are not supported.

# createdb -T template_postgis my_spatial_db

postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis

$ psql -f lwpostgis_upgrade.sql -d your_spatial_database

$ utils/postgis_proc_upgrade.pl lwpostgis.sql > lwpostgis_upgrade.sql

$ pg_dump -Fc olddb > olddb.dump

$ sh utils/postgis_restore.pl lwpostgis.sql newdb olddb.dump -E=UNICODE > restore.log

$ grep ^KEEPING restore.log | less

$ psql newdb -c "ALTER TABLE geometry_columns DROP attrelid" 
$ psql newdb -c "ALTER TABLE geometry_columns DROP varattnum" 
$ psql newdb -c "ALTER TABLE geometry_columns DROP stats"

$ psql newdb 
newdb=> drop spatial_ref_sys; 
DROP 
newdb=> \i spatial_ref_sys.sql

The JDBC extensions provide Java objects corresponding to the internal PostGIS types. These objects can be used to write Java clients which query the PostGIS database and draw or do calculations on the GIS data in PostGIS.

The data loader and dumper are built and installed automatically as part of the PostGIS build. To build and install them manually:

# cd postgis-1.3.3SVN/loader 
# make 
# make install

The loader is called shp2pgsql and converts ESRI Shape files into SQL suitable for loading in PostGIS/PostgreSQL. The dumper is called pgsql2shp and converts PostGIS tables (or queries) into ESRI Shape files. For more verbose documentation, see the online help, and the manual pages.

Guys wana share some good questions of CSTE Exam i found some where in CSTE Group..

****************************************************************************

Q1) The QAI is starting a project to put the CSTE certification online. They will use an automated process for recording candidate information, scheduling candidates for exams, keeping track of results and sending out certificates. Write a brief test plan for this new project?

Ans1:

Test plan of the above will consist of:
a) Objective: To automate the CSTE certification online

b) Identifier: CSTE-AUT/1/India

c) References: Records of earlier CSTE Exams held
Names of the people involved in earlier exams held
CBOK, exam material, application forms, certification

d) Test Items:

The forms of the site for application, re-scheduling, postponing exam etc.
On line tutorials.
Help support provided
CSTE main exam links
Connectivity.
Databases

e) Risks:

Recovery

Correctness

Security
Unauthorized access of the application
Databases Integrity
Redundancy, Configuration management,
portability, Maintainability
Ease of use, ease of operation.

f) Testing Strategy:

White box testing
Black box testing
Stress testing,

Performance testing
Configuration Management,
System testing, Security Testing,
( can add some more techniques for testing)

g) Acceptance Criteria:

Criteria for exit like the requirements specified by user are met fully, the site is fault free, and the application for the main exam is working fine. The functionality is fully satisfied.

h) Suspension or Reject Criteria:

Testing cannot progress if any of the test items do not satisfy all the input data is provided. Enough time is provided.

i) Schedules:

 Schedules given here for each type of testing and reporting results.

j) Environmental Needs:

Tools required for testing. Connectivity provided. Recovery data provided.

k) Training Needs:

 Training of the testers, training of the personnel

l) Approval:

 Approval of the management, users.

m) Glossary:

All the vocabulary support, data dictionaries etc.

Q2) The five dimensions of the Risks are?

Ans2:

a) Technology Integration - What kind of technology are we using a new hardware/software technology. We may not have enough expertise on that. The

technology might not be time proven yet.

 b) Size and Complexity - The Size and the Complexity of the application. e.g Banking applications are huge and more complex

 c) System Environment and Stability - Env (e.g web based might not be stable)

 d) Criticality/Mission Impact - Life critical applications like medical equipment simulation, flight simulation are highly critical. Financial, e-banking are critical as per the financial aspect

 e) Reliability and Integrity - Finally, the application must be reliable and must do what it is intended for...

Q3) Explain testing life cycle?

Ans3:

Test Analysis---Test Plan---Test case Design---Test Execution---Test

Log--------Test Report.

                                                                  |      

^

                                                                  |      

|

Tracking                                                 Defect

Q4) How would u prepare the Test plan for the Project?

Ans4:

Assumptions:-

The requirements are given clearly to u, stating that u have to prepare

Plan for CSTE certification Online by

1. Recording candidate information

2. Scheduling candidates for exams

3. Keeping track of results and

4. Sending out certificates

Test Plan covering the details

1. Who is going to prepare the plan?

2. Which is your reference document for preparing the Plan?

3. What SDLC the project is going to attain in that when testing comes.

4. When Testing starts for each module of the application.

5. What type of testing (Manual or Automation?)

6. Who is going to test it?

7. When he is going to test it

8. Which tools you’re going to use?

9. Plan or give date if training is need for Tools

10. What are the Deliverables?

11. What is the knowledge of the application by the Tester, check if

Training is needed.

12. What level of testing is going to be done?

13. When Test Cases is going to prepared

14. Who is going to review it?

15. Who the Defect Report is reported?

Q5) what activity is done in Acceptance Testing, which is not done in System testing to ensure the Customer requirements?

Ans5:

Main objective of both system and acceptance testing is ensure all the functionalities and requirement are implemented correctly or not. In Acceptance testing. real time test data is used, usually acceptance testing is done by client or clients representative. Here client will check the all functionalities. But in System testing. - project team and testing team should do testing.  Here we have to do all system testing like load, stress, performance etc.  - Its not mandatory that we have to use real time data again its depends on the type of application.

a) Acceptance test is executed by users where as system test is executed by the testers.
b) Acceptance test is the responsibility of the client and is a final check point to accept or reject the software.
c)Acceptance testing involves the actual production environment where as system testing simulates the production environment

d) Acceptance testing involves testing the acceptance test criteria mentioned in the Acceptance test plan and verifying that the product meets those criteria where as system test involves testing the entire system and verifying the performance as a whole.
e) System test is carried out when the entire system is ready where as acceptance tests can be carried out at pre - defined intervals.

Q6) "The top management was feeling that when there are any changes in the technology being used, development schedules etc, it is a waste of time to update the Test Plan also from time to time. Instead, they are emphasizing that you should put your time into testing than working on the test plan.  Your Project Manager asked for your opinion. You have argued that Test Plan is very important and you need to update your test plan from time to time. It is not at all a waste of time and testing activities would be more effective when you have your plan clear. Explain with some metrics; how you would support your argument to have the test plan in place all the time."?

Ans6:

Testing is a process and needs planning; too. The test plan serves as a contract between QA and the project team. It serves as the foundation for the QA team. If you don't plan, plan to fail. QA will not be able to verify the test coverage of the new technology if it is not addressed in the test plan. Further, the test plan will address how the technology will be tested in regards to test factors and if the technology will negatively impact other features.

Without a test plan, we don’t know

a)     What we are going to do

b)     How we are going to do it

c)     How long will it take

d)     Resources required

e)     Cost

Without a documented test plan

a)     The test can not be verified

b)     Coverage can not be analyzed

c)     The test is not repeatable

d)     Test can not be controlled

e)     Test plan is a tool to verify or confirm requirement

f)       Review of test plan can identify gaps and missing or vague requirement

g)     Test plan ensures that each requirement is testable

h)     Planning helps in selection of test cases

i)        Test plan is a dynamic document like any other plan

j)       Test plan defines overall testing objectives and approach

k)      Test design defines what is selected to test and describes expected results

Or

If we keep the TestPlan up-to-date, it will enable:

a) Keep a track of all deliverables as defined in test plan with any
slippages in their schedules. If any slippages are occurring, take
preventive actions. Also enable to estimate  h/w and manpower
resources/efforts, based on technological changes.

b) Test progress S curve (plan,attempted,actual testcases) shall give
a fair indication of the status of testing activity.

c) Technological changes might lead to changes in test strategies.
An updated test plan would enable effective testing coz strategy would
be well defined and updated

d) Ascertain when the testing activity should stop

e) Estimate correct value of Code coverage (Percentage of lines of
code executed per total lines of code) and take necessary action to
test components that cover less code
f) Serve as a basis for testing a similar kind of application in future

Q7) Short form for 11 Quality Factors: - MICE UR FlIRT (not exam related)

Ans7:

M: Maintainability

I: Integrity

C: Correctness

E: Efficiency

U: Usability

R: Reliability

Fl: Flexibility

I: Interoperability

R: Reusability

T: Testability

Q8) What fields would you include in creating a new defect tracking program (used by QA, developers, etc)? (25 points)

Ans8:

It should content following fields:-

Defect Id

Status:- New, Active, Fixed, Resolve, Duplicate, By Design, Closed, Reopen

Assigned to

Source of Defect (Test case or other source)

Stage of origination

Project

Subject

Summary

Description

R&D comments

Reproducible Yes/No

Severity: - Low, Medium, High, Very High, Urgent

Priority: - Low, Medium, High, Very High, Urgent

Detected By

Detected date

Detected in version

Closed in version

Screen print & Logs etc.

Q9) What 3 tools would you purchases for your company for use in testing and justify why you would want them? (this question is in both essay parts, only rephrased. I think 10 points each time)

 Ans9:

# Test management tool  - (Optional)

    why because : Helps in :
                    - Saving time in the creation and duplication of test scripts 
                    -Staffing decisions accurately 
                    -Testing process and implementation
                    - Maintaining documentation and implementation to meet the

                     requirements
                    - Taking corrective steps before the system goes live
                    - Tracking specific information about individual test scripts
                    - Getting updates on daily testing activities
                    - Record test results and produce statistical reports on test   results
# Unit test tool -

       Why because:
           unit test must be performed by the programmers and each class   implemented must have programmer-developed unit tests, for everything that "could possibly break". These tests are to be written during coding of the class, preferably right before implementing a given feature. Tests are run as frequently as possible during development, and all unit tests in the entire system must be running at 100% before any developer releases his code.

# functional/regression test tool -

    If I adopt this tool then i can reduce risks and make the most of limited resources by implementing automated functional and regression testing of critical applications, whereby development and QA teams create reusable test assets that provide in-depth defect analysis and expedite resolution of defects.

    Why because:

         -It will ensure that the quality at every step of delivery
         -It will fill the gap between the development and testing teams
         -it will quickly identify and correct problems and cost- effective

 # Load and stress tool -

    Why because

          It will help us to interpret the data, and point at the most likely performance problems.

# Bug tracking tool -(Optional)

     Why because:

        It is quite hard to keep track of what bugs have been raised, and which of them have been fixed. As well as automating this process, bug tracking tools make it extremely easy to analyze projects using metrics and reports

Q10) what are the points to be emphasized in testing of a system which has multiple workstations for inputting (as against a single workstation system)?

Ans10:

a)     Seduconcurrancy testing :- When one user or console is updating /adding /deleting a record other user should not be allowed to process the same record - Other user should be in wait state

b)     Load test / stress test should be done

c)     Recovery test should be done

d)     Performance testing: - Response time/Transaction completion time

e)     Data validation: - Check if data is saved in correct order, data retrieval is correct

f)       Access control

g)     Database security

h)     Concurrent user test

i)        Update and Rollback

j)       Response time and Server connectivity