KEMBAR78
Software Systems: Data State Within The Integration Layer | PDF | Information Technology | Software Testing
0% found this document useful (0 votes)
116 views8 pages

Software Systems: Data State Within The Integration Layer

The document discusses system integration testing and provides steps to test the data state within the integration layer, database layer, and application layer. It also discusses user acceptance testing and provides typical steps involved, including test planning, designing test cases, executing test cases, documenting defects, resolving issues, and sign off. Finally, it defines quality assurance, quality control, and testing.

Uploaded by

Sakul Koirala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
116 views8 pages

Software Systems: Data State Within The Integration Layer

The document discusses system integration testing and provides steps to test the data state within the integration layer, database layer, and application layer. It also discusses user acceptance testing and provides typical steps involved, including test planning, designing test cases, executing test cases, documenting defects, resolving issues, and sign off. Finally, it defines quality assurance, quality control, and testing.

Uploaded by

Sakul Koirala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

6 + years of experience with below skill set.

Create a Automation Test Suite for a Portfolio Management


Web Applications. Automation Scripts to be developed in Rational RFT toolset. 

System integration testing is the process of verifying the synchronization between two or more
software systems and which can be performed after software system collaboration is completed.

Data state within the integration layer

Integration layer can be a middleware or web service(s) which is act as a media for data imports
and data exports. Perform some data imports and exports and check following steps.

1. Cross check the data properties within the Integration layer with technical/business
specification documents.

- If web service involved with the integration layer then we can use WSDL and XSD against our
web service request for the cross check.

- If middleware involved with the integration layer then we can use data mappings against
middleware logs for the cross check.

Data state within the database layer

1. First check whether all the data have committed to the database layer from the integration
layer.

2. Then check the data properties with the table and column properties with relevant to
technical/business specification documents.

3. Check the data validations/constrains with business specification documents.

4. If there are any processing data within the database layer then check Stored Procedures with
relevant specifications.

5. Investigate the server logs for troubleshooting.

Data state within the Application layer

There is not that much to do with the application layer when we perform a system integration
testing.

1. Mark all the fields from business requirement documents which should be visible in the UI.

2. Create a data map from database fields to application fields and check whether necessary
fields are visible in UI.
3. Check data properties by some positive and negative test cases.

User Acceptance Testing – How to Test?

The user acceptance testing is usually a black box type of testing. In other words, the focus
is on the functionality and the usability of the application rather than the technical aspects.
It is generally assumed that the application would have already undergone Unit, Integration
and System Level Testing. However, it is useful if the User acceptance Testing is carried out
in an environment that closely resembles the real world or production environment.

The steps taken for User Acceptance Testing typically involve one or more of the following:
.......1) User Acceptance Test (UAT) Planning
.......2) Designing UA Test Cases
.......3) Selecting a Team that would execute the (UAT) Test Cases
.......4) Executing Test Cases
.......5) Documenting the Defects found during UAT
.......6) Resolving the issues/Bug Fixing
.......7) Sign Off

Quality Assurance: A set of activities designed to ensure that the development and/or
maintenance process is adequate to ensure a system will meet its objectives.

Quality Control: A set of activities designed to evaluate a developed work product.

Testing: The process of executing a system with the intent of finding defects. (Note that
the "process of executing a system" includes test planning prior to the execution of the
test cases.)

1) What is TFS? What fields do you see in TFS? Where and how did you use it?

1. Team foundation server

Hi, it's a microsoft product. The server-side component is team foundation server (commonly abbreviated
tfs), which comprises two components: the application tier and the data tier. The application tier is a set
of web services that provide access to tfs functionality, and a web portal and document repository
facilitated by windows sharepoint services, whereas the data tier is essentially a microsoft sql server 2005
standard installation that warehouses all the information for tfs. Both tiers are required, but can be
installed on the same or separate servers. Team foundation server contains one or more team projects,
which consists of visual studio solutions, configuration files for team build and team load test agents, and
a single sharepoint repository containing the pertinent documents for the project. It can be used as bug
tracking tool, we can write test cases using tfs, we can publish the results of test cases in it, and we can
use it as a source control repository. If u need more and more info reply to this answer thanks

The main fields are : Project management, work item tracking, version control, Reporting
and team build
What we can do using TFS
We can do all in ALM (Application LifeCycle Management)

1. Source Control, 2. Build automation 3. sharepoint integration 4. Process integation


(Agile/CMMI )5. Bug tracking 6. Reporting 7. Testing

2) What did you use visual Studio for? When did you use it and how did you use it?

Microsoft Visual Studio Team Edition for Software Testers is a first-class testing tool integrated with the
whole Test System product family. By leveraging Microsoft Visual Studio Team Edition for Software
Testers, your test team is able to help provide an essential part of the overall software health picture of
your product development project.

Quality center (requirements, business components, test lab, test plan, defects)

In client server application you have two different components to test. Application is loaded on
server machine while the application exe on every client machine. You will test broadly in
categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This
environment is mostly used in Intranet networks. You are aware of number of clients and servers
and their locations in the test scenario.

Web application is a bit different and complex to test as tester don’t have that much control
over the application. Application is loaded on the server whose location may or may not be
known and no exe is installed on the client machine, you have to test it on different web
browsers. Web applications are supposed to be tested on different browsers and OS platforms so
broadly Web application is tested mainly for browser compatibility and operating system
compatibility, error handling, static pages, backend testing and load testing.

3) What is CMMI and what does it do?

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging
the maturity of the software processes of an organization and for identifying the key
practices that are required to increase the maturity of these processes.
It helps integrate traditionally separate organizational functions, set process improvement goals
and priorities, provide guidance for quality processes, and provide a point of reference for
appraising current processes. 
The benefits you can expect from using CMMI include the following:

 Your organization's activities are explicitly linked to your business objectives.


 Your visibility into the organization's activities is increased to help you ensure that your
product or service meets the customer's expectations.
 You learn from new areas of best practice (e.g., measurement, risk)

4) What is mean by business object? How does it work?

Business Objects is an integrated set of software products that collectively provide business user access
to information from a wide variety of data sources

The Repository. This is a database split into three areas, called domains. The three domains are
Security, which hold user and rights data; Universes (of which more later), and Documents, where report
generation programs are stored.

 Designer. This tool is used to create and maintain Universes.


 Reporter. Appearing on the Start Menu as “Business Objects”, this is the tool used to create and
maintain reports. The ‘program’ generated by Reporter is known as a document, and is stored
in the repository. Reporter is often referred to as ‘Business Objects Full Client’ (BO FC).
Reporter, Designer, and Repository-based Universes form the original core of the Business
Objects offering.
 Web Intelligence. This is a server-based product, and is used to generate reports on business
user computers, in a browser. It has much of the functionality of Reporter, but requires no
footprint on the delivery machine. The name is usually shortened to WebI.
 InfoView is Business Objects’ information portal solution
 Application Foundation is a layer on top of all of the foregoing.

5) How did you prepare RTM and how did you divide it?

RTM is very important in software engineering and it is main thing that developer, QA,
architect must update accordingly. Basically it covers all the relationship of your project
where you can trace if change in requirement or after long time you came and work on
project but you don't remember any thing related to project. You can

Commonly it consist following columns in sheet

Req Id [Unique Id], Use Case Id, Class Id, User Interface Id, Test Case Id

Finally you can trace your requirement...

About Rational ClearQuest


You can use IBM Rational ClearQuest to check the quality of your application or component during each phase
of the development cycle and to track the release in which a feature, enhancement, or bug fix appears.
You can perform the following tasks:

 Submit bug reports and change request records


 View and modify existing records
 Run predefined queries
 Create and run new queries
 Create and run new reports
 View predefined charts and reports

You can submit a change request form to record defects and enhancement requests.
To submit a change request:

1. In Front Desk, click the Change Requests option.


2. If the Current ClearQuest Database does not display the name of the database you want to use, click
Change and log in to a different database.
3. Select a record type in Create Record.
4. Click Go.
5. If the Rational ClearQuest Login window opens, log in to the Rational ClearQuest database.
6. The change request form is displayed. Complete the fields on the Main page.
7. If the change request is part of a UCM project, click the United Change Management tab. Select the
UCM activity that this change request is part of.
8. To submit the change request, click OK.

What is Visio 2000 and how did you work in it?


Visio (is a commercial diagramming program for Microsoft Windows that uses vector graphics to create
diagrams

What is production support system testing (PSS)?


Normally the production support activities include

* Scheduling
* R/3 Job Monitoring
* B/W Job Monitoring
* Taking corrective action for failed data loads.
* Working on some tickets with small changes in reports or in AWB objects.
The activities in a typical Production Support would be as follows:
1. Data Loading - could be using process chains or manual loads.
2. Resolving urgent user issues - helpline activities
3. Modifying BW reports as per the need of the user.
4. Creating aggregates in Prod system
5. Regression testing when version/patch upgrade is done.
6. Creating adhoc hierarchies.
How do you perform integration testing?
To perform integration testing, first, all unit testing has to be completed. Upon completion of unit
testing, integration testing begins. Integration testing is black box testing. The purpose of
integration testing is to ensure distinct components of the application still work in accordance to
customer requirements. Test cases are developed with the express purpose of exercising the
interfaces between the components. This activity is carried out by the test team.
Integration testing is considered complete, when actual results and expected results are either
in line or differences are explainable, or acceptable, based on client input.

What's the difference between STATIC TESTING and DYNAMIC TESTING?

Static Testing: Verification performed with out executing the system code
Dynamic Testing: Verification and validation performed by executing the system code

What is good code?


A good code is code that works, is free of bugs and is readable and maintainable. Organizations
usually have coding standards all developers should adhere to, but every programmer and
software engineer has different ideas about what is best and what are too many or too few
rules. We need to keep in mind that excessive use of rules can stifle both productivity and
creativity. Peer reviews and code analysis tools can be used to check for problems and enforce
standards.
Why back-end testing is required, if we are going to check the front-end ....?
Assume that you're thinking client-server or web. If you test the application on the front end only you
can see if the data was stored and retrievd correctly. You can't see if the servers are in an error state or
not. many server processes are monitored by another process. If they crash, they are restarted. You
can't see that without looking at it.
The data may not be stored correctly either but the front end may have cached data lying around and it
will use that instead. The least you should be doing is verifying the data as stored in the database.
It is easier to test data being transferred on the boundaries and see the results of those transactions
when you can set the data in a driver.
What is Benchmark?
How it is linked with SDLC (Software Development Life Cycle)?
or SDLC and Benchmark are two unrelated things.?
What are the compoments of Benchmark?
In Software Testing where Benchmark fits in?

A Benchmark is a standard to measure against. If you benchmark an application, all future


application changes will be tested and compared against the benchmarked application.
What is a requirements test matrix?
The requirements test matrix is a project management tool for tracking and managing testing
efforts, based on requirements, throughout the project's life cycle.
The requirements test matrix is a table, where requirement descriptions are put in the rows of
the table, and the descriptions of testing efforts are put in the column headers of the same table.

The requirements test matrix is similar to the requirements traceability matrix, which is a
representation of user requirements aligned against system functionality. system testing effort.
What metrics are used for bug tracking?
Metrics that can be used for bug tracking include the followings: the total number of bugs, total
number of bugs that have been fixed, number of new bugs per week, and the number of fixes
per week. Metrics for bug tracking can be used to determine when to stop testing, for example,
when bug rate falls below a certain level. You CAN learn to use defect tracking software.
What is ACH and NACHA?
ACH- Automatic clearing house
ACH. A nationwide electronic funds transfer network which enables participating financial
institutions to distribute electronic credit and debit entries to bank accounts and to settle such
entries.
NACHA:
A membership organization that provides marketing and education assistance and establishes
the rules, standards and procedures that enable Financial Institutions to exchange ACH
payments on a national basis.
What's the SDLC models- waterfall and v-models?
In large scale company first of all they are followed waterfall method. now days mostly
companies are following V models.
model - means the testing involvement starts from the design state itself & continues till system
test.
Phase Testing
Requirements - review
design - review
TR - TUT
then testing phases starts.
So, like this testing makes a perfect V. so we call it V model.
Indicate the flow of activities in the V-model, please look at:
How do you conduct peer reviews?
The peer review, sometimes called PDR, is a formal meeting, more formalized than a walk-
through, and typically consists of 3-10 people including the test lead, task lead (the author of
whatever is being reviewed) and a facilitator (to make notes).
When testing the password field, what is your focus?
When testing the password field, one needs to focus on encryption; one needs to verify that the
passwords are encrypted.

You might also like