Professional Documents
Culture Documents
LP-II Oral Question Bank
LP-II Oral Question Bank
LP-II Oral Question Bank
ANS:- There are three different Data Warehousing Schemas are as follows
1) Star Schema
2) Snowflake Schema
3) Fact constellation Schema
ANS:-
In star schema, The fact tables While in snowflake schema, The fact tables,
and the dimension tables are dimension tables as well as sub dimension
1. contained. tables are contained.
It takes less time for the While it takes more time than star schema
4. execution of queries. for the execution of queries.
Supervised Learning can be used for 2 different types Unsupervised Learning can be used for 2
of problems i.e. regression and classification different types of problems i.e. clustering
and association.
Input Data is provided to the model along with the Only input data is provided in
output in the Supervised Learning. Unsupervised Learning.
Output is predicted by the Supervised Learning. Hidden patterns in the data can be found
using the unsupervised learning model.
Labeled data is used to train supervised learning Unlabeled data is used to train
algorithms. unsupervised learning algorithms.
Accurate results are produced using a supervised The accuracy of results produced are less
learning model. in unsupervised learning models.
Training the model to predict output when a new data Finding useful insights, hidden patterns
is provided is the objective of Supervised Learning. from the unknown dataset is the objective
of the unsupervised learning.
Supervised Learning includes various algorithms such Unsupervised Learning includes various
as Bayesian Logic, Decision Tree, Logistic Regression, algorithms like KNN, Apriori Algorithm,
Linear Regression, Multi-class Classification, Support and Clustering.
Vector Machine etc.
To assess whether right output is being predicted, No feedback will be taken by the
direct feedback is accepted by the Supervised unsupervised learning model.
Learning Model.
In Supervised Learning, for right prediction of output, Unsupervised Learning has more
the model has to be trained for each data, hence resemblance to Artificial Intelligence, as it
Supervised Learning does not have close keeps learning new things with more
resemblance to Artificial Intelligence. experience.
Number of classes are known in Supervised Learning. Number of classes are not known in
Unsupervised Learning
In scenarios where one is aware of output and input In the scenarios where one is not aware of
data, supervised learning can be used. output data, but is only aware of the input
data then Unsupervised Learning could be
used.
Supervised Learning will use off-line analysis Unsupervised Learning uses Real time
analysis of data.
Some of the applications of Supervised Learning are Some of the applications of Unsupervised
Spam detection, handwriting detection, pattern Learning are detecting fraudulent
recognition, speech recognition etc. transactions, data preprocessing etc.
1) Partitioning Clustering Method. In this method, let us say that “m” partition is
done on the “p” objects of the database. ...
2) Hierarchical Clustering Methods. ...
3) Density-Based Clustering Method. ...
4) Grid-Based Clustering Method. ...
5) Model-Based Clustering Methods. ...
6) Constraint-Based Clustering Method.
14. What is Weka Tool? Explain the Step to Perform Clustering on Sample data set?
ANS:-
The WEKA Simple K-Means algorithm uses Euclidean distance measure to compute
distances between instances and clusters. To perform clustering, select the "Cluster"
tab in the Explorer and click on the "Choose" button. This results in a drop down list
of available clustering algorithms.
2. These frequent itemsets and the minimum confidence constraint are used to
compose the rules. Finding all frequent itemsets in a data set is a complex procedure
since it involves analyzing all possible itemsets.
3.- Create a process with "Read from File" operator and configure it as follow:
Few things to notice:
- The amount of "\" in the path is mandatory, 3 after the Drive and 2 on the folder.
- On this example the 'Administrator' user is used directly, this can be changed using process
variables or even without a user if Process Automation service is configured to be executed
by specific user with higher permissions:
When this process is executed, the result is shown as follow:
The operator shows the following information:
STQA Questions:-
Q #1) What is the difference between Quality Assurance, Quality Control, and
Testing?
Answer: Quality Assurance is the process of planning and defining the way of
monitoring and implementing the quality(test) processes within a team and
organization. This method defines and sets the quality standards of the projects.
Quality Control is the process of finding defects and providing suggestions to
improve the quality of the software. The methods used by Quality Control are
usually established by quality assurance. It is the primary responsibility of the
testing team to implement quality control.
Here, the main focus is on finding bugs and the testing teams work as a quality
gatekeeper.
Q #3) What is the difference between the Test Plan and Test Strategy?
Answer: Test Strategy is at a higher level, mostly created by the Project Manager
which demonstrates the overall approach of the testing for the entire project,
whereas the Test plan depicts how the testing should be performed for a
particular application, falling under a project.
Q #4) Can you explain the Software Testing Life Cycle?
Answer: Software Testing Life Cycle refers to a testing process that has specific
steps to be executed in a definite sequence to ensure that the quality goals have
been met.
Q #5) How do you define a format of writing a good test case?
Answer: The format of Test Case includes:
• Test case ID
• Test case description
• Severity
• Priority
• Environment
• Build version
• Steps to execute
• Expected results
• Actual results
Q #6) What is a good test case?
Answer: In simple words, a good test case is one that finds a defect. But all test
case will not find defects, so a good test case can also be one which has all the
prescribed details and coverage.
Q #7) What would you do if you have a large suite to execute in very less time?
Answer: In case we have less time and have to execute the larger volume of test
cases, we should prioritize the test case and execute the high priority test cases
first and then move on to the lower priority ones.
This way we can make sure that the important aspects of the software are
tested.
Alternatively, we may also seek customer preference that which is the most
important function of the software according to them, and we should start
testing from those areas and then gradually move to those areas which are of
less importance.
Q #8) Do you think QA’s can also participate to resolve production issues?
Answer: Definitely!! It would be a good learning curve for QA’s to participate in
resolving production issues. Many time production issues could be resolved by
clearing the logs or making some registry settings or by restarting the services.
These kinds of environmental issues could be very well fixed by the QA team.
Also, if QA has an insight into resolving the production issues, they may include
them while writing the test cases, and this way they can contribute to improve
quality and try to minimize the production defects.
Q #9) Suppose you find a bug in production, how would you make sure that the
same bug is not introduced again?
Answer: The best way is to immediately write a test case for the production
defect and include it in the regression suite. This way we ensure that the bug
does not get introduced again.
Also, we can think of alternate test cases or similar kinds of test cases and
include them in our planned execution.
Q #12) How would you ensure that your testing is complete and has good
coverage?
Answer: Requirement Traceability Matrix and Test coverage matrices will help us
to determine that our test cases have good coverage.
Requirement traceability matrix will help us to determine that the test conditions
are enough so that all the requirements are covered. Coverage matrices will help
us to determine that the test cases are enough to satisfy all the identified test
conditions in RTM.
Q #13) What are the different artifacts you refer to when you write the test
cases?
Answer: The main artifacts used are:
• Functional requirement specification
• Requirement understanding document
• Use Cases
• Wireframes
• User Stories
• Acceptance criteria
• Many a time UAT test cases
Q #14) Have you ever managed writing the test cases without having any
documents?
Answer: Yes, there are cases when we have a situation where we have to write
test cases without having any concrete documents.
In that case, the best way is to:
• Collaborate with the BA and development team.
• Dig into mails which have some information.
• Dig into older test cases/regression suite
• If the feature is new, try to read the wiki pages or help of the
application to have an idea
• Sit with the developer and try to understand the changes being
made.
• Based on your understanding, identify the test condition and send it
to BA or stakeholders to review them.
Q #15) What is meant by Verification and Validation?
Answer:
Validation is the process of evaluating the final product to check whether the
software meets the business needs. The test execution which we do in our day to
day life is the validation activity which includes smoke testing, functional testing,
regression testing, systems testing, etc.
Verification is a process of evaluating the intermediary work products of a
software development lifecycle to check if we are in the correct track of creating
the final product.
Q #16) What are the different verification techniques you know?
Answer: Verification techniques are static. There are 3 verification techniques.
These are explained as follows:
(i) Review – This is a method by which the code/test cases are examined by the
individual other than the author who has produced it. It is one of the easy and
best ways to ensure coverage and quality.
(ii) Inspection – This is a technical and disciplined way to examine and correct
the defects in the test artifact or code. Because it is disciplined, it has various
roles:
• Moderator – Facilitates the entire inspection meeting.
• Recorder – Records the minutes of the meeting, defects occurred,
and other points discussed.
• Reader – Read out the document/code. The leader also leads to the
entire inspection meeting.
• Producer – The author. They are ultimately responsible to update
their document/code as per the comments.
• Reviewer – All the team members can be considered as a reviewer.
This role can also be played by some group of experts is the project
demands.
(iii) Walkthrough – This is a process in which the author of the document/code
reads the content and gets the feedback. This is mostly a kind of FYI (For Your
Information) session rather than seeking corrections.
Q #17) What is the difference between Load and Stress testing?
Answer:
Stress Testing is a technique which validates the behavior of the system when it
executes under stress. To explain, we reduce the resources and check the
behavior of the system. We first understand the upper limit of the system and
gradually reduce the resources and check the system behavior.
In Load testing, we validate the system behavior under the expected load. The
load can be of concurrent user or resources accessing the system at the same
time.
Q #18) In case you have any doubts regarding your project, how do you approach?
Answer: In case of any doubts, first, try to get it cleared by reading the available
artifacts/application help. In case of doubts that persist, ask an immediate
supervisor or the senior member of your team.
Business Analysts can also be a good choice to ask doubts. We can also convey
our queries with the development team in case of any other doubts. The last
option would be to follow up with the manager and finally to the stakeholders.
It’s very important to understand the entire testing lifecycle and should be able
to suggest changes in our process if required. The goal is to deliver high-quality
software and in that way, a QA should take all the necessary measures to
improve the process and way the testing team executes the tests.