Forwarded from Selenium/Playwright/SQL/API/TOSCA/ Katalon Testing (Automation & Manual Testing) (admin)
A ________ is an occurrence where the software does not behave as expected
Anonymous Quiz
48%
Comment if you know
52%
Answer
Forwarded from Selenium/Playwright/SQL/API/TOSCA/ Katalon Testing (Automation & Manual Testing) (admin)
A ________ is an occurrence where the software does not behave as expected.
Anonymous Quiz
33%
Answer
67%
I know answer
Forwarded from Selenium/Playwright/SQL/API/TOSCA/ Katalon Testing (Automation & Manual Testing) (admin)
________ testing is done to ensure that the new code does not adversely affect the existing functionality of the product
Anonymous Quiz
62%
Answer
38%
Self Answer
Forwarded from Selenium/Playwright/SQL/API/TOSCA/ Katalon Testing (Automation & Manual Testing) (admin)
1. **What is the main objective of manual testing?**
Anonymous Quiz
42%
If u know comment
58%
For answer click on this
Forwarded from Selenium/Playwright/SQL/API/TOSCA/ Katalon Testing (Automation & Manual Testing) (admin)
2. **Which of the following is a type of manual testing?**
Anonymous Quiz
45%
Unit Testing
1%
Load Testing
47%
System Testing
6%
Performance Testing
Forwarded from Performance Testing Mentor
Q2. Amongst which of the following is / are the intent of Performance testing.
Anonymous Quiz
21%
To understand how the system responds as loading
8%
To collect metrics that will lead to design modifications to improve performance
8%
Only B
63%
Both A and B
Forwarded from Surya's techno world (๊ฏฑืื
ึฯ
ืื
๊ญืื
แจฎืื
ึฎ๊ซถษืื
ึฎ ฦืื
ึ๊ชฑืื
๊ญืื
ษืื
ึฎ๊ชืื
. โโโโSBKโโโโ)
Which of the following is an important principle in performance testing?
Anonymous Poll
16%
The tests should be easy to create and understand
13%
The test results must be reproducible when the system under test is unchanged
34%
The tests should be executed in the production environment to provide the most accurate results
38%
The test results should match the stakeholdersโ expectations for system performance
Forwarded from Performance Testing Mentor
Q5. Which of the following is the best description of load testing?
Anonymous Quiz
42%
ability of the system to handle loads that are gradually increased to reach the expected maximum
37%
the ability of the system to handle loads that are at or beyond the expected peak load
11%
It focuses on the ability of the system to meet future efficiency requirements
11%
It focuses on the ability of the system to respond to quick and extreme changes in load
Forwarded from Performance Testing Mentor
Q6. Which of the following performance testing activities should occur during unit testing?
Anonymous Quiz
45%
Testing end-to-end behavior under various load conditions
15%
Testing data flows and workflows across interfaces
15%
Testing key use cases and workflows using a top-down approach
25%
Testing to evaluate resource utilization and potential bottlenecks
Which SQL clause is used to filter groups of rows based on a condition? @qa_evaluation
Anonymous Quiz
28%
A) WHERE
51%
B) GROUP BY
9%
C) HAVING
11%
D) ORDER BY
What is the primary purpose of an index in SQL? Join @qa_evaluation
Anonymous Quiz
21%
A) To store large objects
8%
B) To enforce referential integrity
50%
C) To speed up retrieval of rows
21%
D) To prevent data redundancy
Though activities in the Fundamental test process may overlap or occur concurrently, identify the sequential process. i) Test Implementation and Execution ii) Test Closure activitiesiii) Evaluating exit criteria and reporting iv) Test Analysis and Design
Anonymous Quiz
0%
i-iii-ii-iv
100%
iv-i-iii-ii
0%
i-ii-iii-iv
0%
iii-ii-iv-i
Which SQL function is used to calculate the cumulative sum of a column? Join @qa_evaluation
Anonymous Quiz
48%
A) SUM()
39%
B) CUME_SUM()
9%
C) RUNNING_SUM()
4%
D) ROW_NUMBER()
Creating UI/UX test cases involves considering various scenarios to ensure a smooth and user-friendly experience. Here are some common scenarios along with example test cases:
### 1. Navigation
- Test Case 1: Main Navigation Menu
- Description: Verify that all links in the main navigation menu are working and lead to the correct pages.
- Steps:
1. Open the application.
2. Click on each item in the main navigation menu.
- Expected Result: Each click should navigate to the corresponding page without any errors.
- Test Case 2: Breadcrumb Navigation
- Description: Verify that breadcrumb navigation is working correctly and reflects the user's current position.
- Steps:
1. Navigate to a sub-page.
2. Check the breadcrumb links.
3. Click on each breadcrumb link.
- Expected Result: Breadcrumb links should navigate to the corresponding parent pages.
### 2. Forms and Inputs
- Test Case 1: Form Submission with Valid Data
- Description: Verify that a form submits successfully with valid data.
- Steps:
1. Open the form page.
2. Enter valid data into all required fields.
3. Click on the submit button.
- Expected Result: The form should submit successfully, and a success message should be displayed.
- Test Case 2: Form Validation with Invalid Data
- Description: Verify that form validation works when entering invalid data.
- Steps:
1. Open the form page.
2. Enter invalid data into one or more fields.
3. Attempt to submit the form.
- Expected Result: The form should not submit, and appropriate error messages should be displayed for each invalid field.
### 3. Responsive Design
- Test Case 1: Mobile Responsiveness
- Description: Verify that the application is responsive on mobile devices.
- Steps:
1. Open the application on a mobile device or use a browserโs developer tools to simulate a mobile device.
2. Navigate through various pages.
- Expected Result: The application should display correctly without horizontal scrolling, and elements should be appropriately sized.
- Test Case 2: Tablet Responsiveness
- Description: Verify that the application is responsive on tablet devices.
- Steps:
1. Open the application on a tablet device or use a browserโs developer tools to simulate a tablet device.
2. Navigate through various pages.
- Expected Result: The application should display correctly without horizontal scrolling, and elements should be appropriately sized.
### 4. Usability
- Test Case 1: Accessibility Compliance
- Description: Verify that the application complies with accessibility standards (e.g., WCAG).
- Steps:
1. Use an accessibility checker tool to evaluate the application.
- Expected Result: The application should pass the accessibility checks without significant issues.
- Test Case 2: User Feedback and Confirmation Messages
- Description: Verify that user actions provide appropriate feedback and confirmation messages.
- Steps:
1. Perform actions such as form submissions, deletions, and updates.
- Expected Result: Each action should provide clear feedback or confirmation to the user.
### 5. Performance
- Test Case 1: Load Time
- Description: Verify that the application loads within an acceptable time frame.
- Steps:
1. Measure the time taken to load the homepage and other critical pages.
- Expected Result: Pages should load within the defined performance thresholds.
- Test Case 2: Interactive Element Response Time
- Description: Verify that interactive elements (e.g., buttons, links) respond promptly.
- Steps:
1. Click on various interactive elements.
- Expected Result: Interactive elements should respond within a reasonable time frame, without noticeable delays.
### 6. Content and Layout
- Test Case 1: Consistent Layout
- Description: Verify that the layout is consistent across different pages.
- Steps:
1. Navigate through various pages.
2. Observe the layout and structure.
- Expected Result: The layout should be consistent and uniform across all pages.
#Testcase #manual
### 1. Navigation
- Test Case 1: Main Navigation Menu
- Description: Verify that all links in the main navigation menu are working and lead to the correct pages.
- Steps:
1. Open the application.
2. Click on each item in the main navigation menu.
- Expected Result: Each click should navigate to the corresponding page without any errors.
- Test Case 2: Breadcrumb Navigation
- Description: Verify that breadcrumb navigation is working correctly and reflects the user's current position.
- Steps:
1. Navigate to a sub-page.
2. Check the breadcrumb links.
3. Click on each breadcrumb link.
- Expected Result: Breadcrumb links should navigate to the corresponding parent pages.
### 2. Forms and Inputs
- Test Case 1: Form Submission with Valid Data
- Description: Verify that a form submits successfully with valid data.
- Steps:
1. Open the form page.
2. Enter valid data into all required fields.
3. Click on the submit button.
- Expected Result: The form should submit successfully, and a success message should be displayed.
- Test Case 2: Form Validation with Invalid Data
- Description: Verify that form validation works when entering invalid data.
- Steps:
1. Open the form page.
2. Enter invalid data into one or more fields.
3. Attempt to submit the form.
- Expected Result: The form should not submit, and appropriate error messages should be displayed for each invalid field.
### 3. Responsive Design
- Test Case 1: Mobile Responsiveness
- Description: Verify that the application is responsive on mobile devices.
- Steps:
1. Open the application on a mobile device or use a browserโs developer tools to simulate a mobile device.
2. Navigate through various pages.
- Expected Result: The application should display correctly without horizontal scrolling, and elements should be appropriately sized.
- Test Case 2: Tablet Responsiveness
- Description: Verify that the application is responsive on tablet devices.
- Steps:
1. Open the application on a tablet device or use a browserโs developer tools to simulate a tablet device.
2. Navigate through various pages.
- Expected Result: The application should display correctly without horizontal scrolling, and elements should be appropriately sized.
### 4. Usability
- Test Case 1: Accessibility Compliance
- Description: Verify that the application complies with accessibility standards (e.g., WCAG).
- Steps:
1. Use an accessibility checker tool to evaluate the application.
- Expected Result: The application should pass the accessibility checks without significant issues.
- Test Case 2: User Feedback and Confirmation Messages
- Description: Verify that user actions provide appropriate feedback and confirmation messages.
- Steps:
1. Perform actions such as form submissions, deletions, and updates.
- Expected Result: Each action should provide clear feedback or confirmation to the user.
### 5. Performance
- Test Case 1: Load Time
- Description: Verify that the application loads within an acceptable time frame.
- Steps:
1. Measure the time taken to load the homepage and other critical pages.
- Expected Result: Pages should load within the defined performance thresholds.
- Test Case 2: Interactive Element Response Time
- Description: Verify that interactive elements (e.g., buttons, links) respond promptly.
- Steps:
1. Click on various interactive elements.
- Expected Result: Interactive elements should respond within a reasonable time frame, without noticeable delays.
### 6. Content and Layout
- Test Case 1: Consistent Layout
- Description: Verify that the layout is consistent across different pages.
- Steps:
1. Navigate through various pages.
2. Observe the layout and structure.
- Expected Result: The layout should be consistent and uniform across all pages.
#Testcase #manual
- Test Case 2: Content Accuracy
- Description: Verify that all text content is accurate and free of typos.
- Steps:
1. Review the text content on various pages.
- Expected Result: The text content should be accurate, correctly formatted, and free of spelling or grammatical errors.
These test cases can be further customized based on the specific requirements and features of your application.
#manual #Testcase
- Description: Verify that all text content is accurate and free of typos.
- Steps:
1. Review the text content on various pages.
- Expected Result: The text content should be accurate, correctly formatted, and free of spelling or grammatical errors.
These test cases can be further customized based on the specific requirements and features of your application.
#manual #Testcase
Selenium with Java in Visual Studio Code (VS Code) for testing. Hereโs a basic guide to get you started:
1. Install Java Development Kit (JDK):
- Download and install the JDK from Oracle's website.
- Set up the environment variables JAVA_HOME and PATH to point to your JDK installation.
2. Install VS Code:
- Download and install Visual Studio Code from here.
3. Install Java Extensions for VS Code:
- Open VS Code.
- Go to the Extensions view (Ctrl+Shift+X).
- Install the following extensions:
- Language Support for Java(TM) by Red Hat
- Debugger for Java
- Java Test Runner
- Maven for Java (optional, if you want to use Maven)
4. Set Up a Selenium Project:
- Open VS Code and create a new folder for your project.
- Open a terminal in VS Code (Ctrl+``).
- If youโre using Maven, you can create a new Maven project by running:
mvn archetype:generate -DgroupId=com.example -DartifactId=selenium-project -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false
cd selenium-project
- If youโre not using Maven, create a new folder structure:
selenium-project
โโโ src
โ โโโ main
โ โโโ test
โโโ lib
5. Add Selenium Dependencies:
- If using Maven, add Selenium dependencies to your pom.xml:
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>4.0.0</version>
</dependency>
</dependencies>
- If not using Maven, download Selenium JARs from here and place them in the lib folder. Then, add them to your classpath.
6. Write Your First Test:
- Create a new Java class in the src/test directory, for example, FirstTest.java`:
```java
package com.example;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
public class FirstTest {
public static void main(String[] args) {
// Set the path to the chromedriver executable
System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
// Initialize a new WebDriver instance
WebDriver driver = new ChromeDriver();
// Open a website
driver.get("https://www.example.com");
// Close the browser
driver.quit();
}
#Selenium #Vscode
1. Install Java Development Kit (JDK):
- Download and install the JDK from Oracle's website.
- Set up the environment variables JAVA_HOME and PATH to point to your JDK installation.
2. Install VS Code:
- Download and install Visual Studio Code from here.
3. Install Java Extensions for VS Code:
- Open VS Code.
- Go to the Extensions view (Ctrl+Shift+X).
- Install the following extensions:
- Language Support for Java(TM) by Red Hat
- Debugger for Java
- Java Test Runner
- Maven for Java (optional, if you want to use Maven)
4. Set Up a Selenium Project:
- Open VS Code and create a new folder for your project.
- Open a terminal in VS Code (Ctrl+``).
- If youโre using Maven, you can create a new Maven project by running:
mvn archetype:generate -DgroupId=com.example -DartifactId=selenium-project -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false
cd selenium-project
- If youโre not using Maven, create a new folder structure:
selenium-project
โโโ src
โ โโโ main
โ โโโ test
โโโ lib
5. Add Selenium Dependencies:
- If using Maven, add Selenium dependencies to your pom.xml:
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>4.0.0</version>
</dependency>
</dependencies>
- If not using Maven, download Selenium JARs from here and place them in the lib folder. Then, add them to your classpath.
6. Write Your First Test:
- Create a new Java class in the src/test directory, for example, FirstTest.java`:
```java
package com.example;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
public class FirstTest {
public static void main(String[] args) {
// Set the path to the chromedriver executable
System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
// Initialize a new WebDriver instance
WebDriver driver = new ChromeDriver();
// Open a website
driver.get("https://www.example.com");
// Close the browser
driver.quit();
}
#Selenium #Vscode
๐1
Performance Testing of any Web Application is?
Anonymous Quiz
19%
Functional testing
81%
Non Functional testing
๐1
Which of the following is NOT a Test Level?
Anonymous Quiz
21%
Regression Testing
33%
Unit Testing
3%
Integration Testing
9%
System Testing
34%
Acceptance Testing
๐2
Which of the following tool does NOT support #Web #Automation?
Anonymous Quiz
5%
Selenium
48%
Postman
15%
Katalon studio
11%
Tosca
3%
Playwright
11%
Cypress
8%
WebdriverlO
๐1
8 Types of API Tests every SDET should know!
1) Smoke Tests: Validating bare minimum crucial AP
calls are working for application.
Tools: Postman, Swagger, Manual Tests
2) Functional Tests: Validating each API for its prominent
functionality. Like Post requests for data creation and
validating in Database whether data sent is created in
right table, structure etc.
Tools: RestAssured, Locust, Gatling, Requests, Postman
with manual Db validation etc.
3) Integration Tests: Validating multiple requests in sync
like calling Post rqst and then Get rqst to validate
whether data is created or not.
Tools: Postman, Requests. RestAssured Locust etc
4) Load Tests: Validating the load capacity of APIs. This
is crucial when user footfall increases.
Tools: JMeter, LoadRunner, Locust, Gatling etc.
5) Stress Tests: Breaking the APIs. This helps to know
about the threshold.
Tools: JMeter, LoadRunner, Locust, Gatling etc
6) Security Testing: Validating external threats if any for
APIs.
Tools: Pynt, OWASP top 10 vulnerabilities with BurpSuite
etc.
7) Fuzz Tests: Validating APIs and servers with sending
unexpected data and validate the response received.
Tools: Postman, Requests, RestAssured etc.
8) Regression Tests: Validating new changes made in
application or APIs should not break existing
functionality.
Tools: Postman, Requests, RestAssured etc.
Join @qa_evaluation
#API
1) Smoke Tests: Validating bare minimum crucial AP
calls are working for application.
Tools: Postman, Swagger, Manual Tests
2) Functional Tests: Validating each API for its prominent
functionality. Like Post requests for data creation and
validating in Database whether data sent is created in
right table, structure etc.
Tools: RestAssured, Locust, Gatling, Requests, Postman
with manual Db validation etc.
3) Integration Tests: Validating multiple requests in sync
like calling Post rqst and then Get rqst to validate
whether data is created or not.
Tools: Postman, Requests. RestAssured Locust etc
4) Load Tests: Validating the load capacity of APIs. This
is crucial when user footfall increases.
Tools: JMeter, LoadRunner, Locust, Gatling etc.
5) Stress Tests: Breaking the APIs. This helps to know
about the threshold.
Tools: JMeter, LoadRunner, Locust, Gatling etc
6) Security Testing: Validating external threats if any for
APIs.
Tools: Pynt, OWASP top 10 vulnerabilities with BurpSuite
etc.
7) Fuzz Tests: Validating APIs and servers with sending
unexpected data and validate the response received.
Tools: Postman, Requests, RestAssured etc.
8) Regression Tests: Validating new changes made in
application or APIs should not break existing
functionality.
Tools: Postman, Requests, RestAssured etc.
Join @qa_evaluation
#API
๐1