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
Git basics:
1. git init -> The git init command creates a new Git repository, which can be used to start a new project with Git.
2. git remote add origin -> The git remote add origin command is used to add a remote repository to your local Git repository.
3. git add. -> The git add command adds a change in the working directory to the staging area.
4. git commit -m 'message' -> The git commit command is what you'll use to take all of the changes that have been made locally and push them up to a remote repository.
5. git push -> sends changes (commits) from a local repository to a remote repository
6. git push origin branch_name -> git push origin is a git command that pushes a local branch(es) to a remote repository (origin).
7. VIM editor edit -> Press Escape and press 'l' for edit
8. VIM editor save and exit -> Press Escape and enter wq (wq!).
9. git log -> The git log command displays committed snapshots.
10. git branch -> see the branches in your repo
11. git branch "branch_name" -> create new branch - it will create in local git repo
12. git push origin "branch_name" - > to push created branch from local to remote repo
13. it checkout -b "branch_name" -> Create new branch and switch to newly created branch
14. git checkout branch_name -> to switch to specific branch
15. git push origin --delete branch_name -> delete branch from the remote repo
16. git branch --delete branch_name -> delete branch from the local repo
17. 17. git restore --staged <file_name> -> The "restore" command helps to unstage or even discard uncommitted local changes. - single file
18. git reset -> unstaging all files
19. git reset --hard -> unstaging and reset all changes from the working directory.
20. git rm -f < file_name> - remove from staging area and working
directory 21. git rm --cached < file_name> - remove from staging area
22. git push-force - forcefully push to specific branch without checking any conflict
23. git push origin --delete <branch_name> -> delete the branch from the remote repo
24. git branch -D <branch_name> -> forcefully delete from the local branch
25. git pull origin master - pull code from the master if there is any merge conflict
26. 26. git branch -m <old_branch_name> <new_branch_name> -> rename of existing branch in git local repo
27. git push origin :<old_name> <new_name> -> rename branch in remote repo
28. git revert commit_ID -> The git revert command is used for undoing changes to a repository's commit history.
29. git push - push reverted changes in respected branch
30. git detached HEAD - In Git, the detached HEAD state occurs when the HEAD does not point to a branch, but instead points to a specific commit or the remote repository.
31. git cherry-pick - In Git, cherry- picking is taking a single commit from one branch and adding it as the latest commit on another branch.
#Git #Github
1. git init -> The git init command creates a new Git repository, which can be used to start a new project with Git.
2. git remote add origin -> The git remote add origin command is used to add a remote repository to your local Git repository.
3. git add. -> The git add command adds a change in the working directory to the staging area.
4. git commit -m 'message' -> The git commit command is what you'll use to take all of the changes that have been made locally and push them up to a remote repository.
5. git push -> sends changes (commits) from a local repository to a remote repository
6. git push origin branch_name -> git push origin is a git command that pushes a local branch(es) to a remote repository (origin).
7. VIM editor edit -> Press Escape and press 'l' for edit
8. VIM editor save and exit -> Press Escape and enter wq (wq!).
9. git log -> The git log command displays committed snapshots.
10. git branch -> see the branches in your repo
11. git branch "branch_name" -> create new branch - it will create in local git repo
12. git push origin "branch_name" - > to push created branch from local to remote repo
13. it checkout -b "branch_name" -> Create new branch and switch to newly created branch
14. git checkout branch_name -> to switch to specific branch
15. git push origin --delete branch_name -> delete branch from the remote repo
16. git branch --delete branch_name -> delete branch from the local repo
17. 17. git restore --staged <file_name> -> The "restore" command helps to unstage or even discard uncommitted local changes. - single file
18. git reset -> unstaging all files
19. git reset --hard -> unstaging and reset all changes from the working directory.
20. git rm -f < file_name> - remove from staging area and working
directory 21. git rm --cached < file_name> - remove from staging area
22. git push-force - forcefully push to specific branch without checking any conflict
23. git push origin --delete <branch_name> -> delete the branch from the remote repo
24. git branch -D <branch_name> -> forcefully delete from the local branch
25. git pull origin master - pull code from the master if there is any merge conflict
26. 26. git branch -m <old_branch_name> <new_branch_name> -> rename of existing branch in git local repo
27. git push origin :<old_name> <new_name> -> rename branch in remote repo
28. git revert commit_ID -> The git revert command is used for undoing changes to a repository's commit history.
29. git push - push reverted changes in respected branch
30. git detached HEAD - In Git, the detached HEAD state occurs when the HEAD does not point to a branch, but instead points to a specific commit or the remote repository.
31. git cherry-pick - In Git, cherry- picking is taking a single commit from one branch and adding it as the latest commit on another branch.
#Git #Github
👍1
Your team is responsible for automated testing in a CI/CD pipeline. During a code deployment, a critical bug is discovered in the production environment. What should you prioritize as your immediate action?
Anonymous Quiz
36%
Roll back the deployment to the previous version
47%
Investigate the bug's root cause and impact on users
9%
Resign from the team and look for brighter options
8%
Continue with the deployment and address thebug later
👍1
SDLC (Software Development Life Cycle) Quality Analyst:
*Quiz: SDLC Quality Analyst*
*Section 1: Fundamentals*
1. What is the primary goal of the SDLC process?
a) To deliver software quickly
b) To ensure software quality
c) To reduce development costs
d) To increase customer satisfaction
Answer: b) To ensure software quality
1. Which SDLC phase involves testing and validation?
a) Requirements gathering
b) Design
c) Implementation
d) Testing and Quality Assurance
Answer: d) Testing and Quality Assurance
*Section 2: Testing*
1. What is the difference between black box and white box testing?
a) Black box testing focuses on internal code, while white box testing focuses on external functionality
b) Black box testing focuses on external functionality, while white box testing focuses on internal code
c) Black box testing is manual, while white box testing is automated
d) Black box testing is automated, while white box testing is manual
Answer: b) Black box testing focuses on external functionality, while white box testing focuses on internal code
1. What is the purpose of regression testing?
a) To test new features
b) To ensure changes didn't break existing functionality
c) To test system performance
d) To test user interface
Answer: b) To ensure changes didn't break existing functionality
*Section 3: Quality Assurance*
1. What is the role of a Quality Analyst in the SDLC process?
a) To write code
b) To design software architecture
c) To ensure software meets requirements and standards
d) To manage project timelines
Answer: c) To ensure software meets requirements and standards
1. What is the difference between quality assurance and quality control?
a) Quality assurance focuses on prevention, while quality control focuses on detection
b) Quality assurance focuses on detection, while quality control focuses on prevention
c) Quality assurance is manual, while quality control is automated
d) Quality assurance is automated, while quality control is manual
Answer: a) Quality assurance focuses on prevention, while quality control focuses on detection
*Section 4: SDLC Methodologies*
1. What is Agile methodology?
a) A linear approach to software development
b) An iterative and incremental approach to software development
c) A hybrid approach to software development
d) A waterfall approach to software development
Answer: b) An iterative and incremental approach to software development
1. What is the purpose of Continuous Integration (CI) in Agile?
a) To integrate code changes frequently
b) To test software manually
c) To design software architecture
d) To manage project timelines
Answer: a) To integrate code changes frequently
#SDLC
*Quiz: SDLC Quality Analyst*
*Section 1: Fundamentals*
1. What is the primary goal of the SDLC process?
a) To deliver software quickly
b) To ensure software quality
c) To reduce development costs
d) To increase customer satisfaction
Answer: b) To ensure software quality
1. Which SDLC phase involves testing and validation?
a) Requirements gathering
b) Design
c) Implementation
d) Testing and Quality Assurance
Answer: d) Testing and Quality Assurance
*Section 2: Testing*
1. What is the difference between black box and white box testing?
a) Black box testing focuses on internal code, while white box testing focuses on external functionality
b) Black box testing focuses on external functionality, while white box testing focuses on internal code
c) Black box testing is manual, while white box testing is automated
d) Black box testing is automated, while white box testing is manual
Answer: b) Black box testing focuses on external functionality, while white box testing focuses on internal code
1. What is the purpose of regression testing?
a) To test new features
b) To ensure changes didn't break existing functionality
c) To test system performance
d) To test user interface
Answer: b) To ensure changes didn't break existing functionality
*Section 3: Quality Assurance*
1. What is the role of a Quality Analyst in the SDLC process?
a) To write code
b) To design software architecture
c) To ensure software meets requirements and standards
d) To manage project timelines
Answer: c) To ensure software meets requirements and standards
1. What is the difference between quality assurance and quality control?
a) Quality assurance focuses on prevention, while quality control focuses on detection
b) Quality assurance focuses on detection, while quality control focuses on prevention
c) Quality assurance is manual, while quality control is automated
d) Quality assurance is automated, while quality control is manual
Answer: a) Quality assurance focuses on prevention, while quality control focuses on detection
*Section 4: SDLC Methodologies*
1. What is Agile methodology?
a) A linear approach to software development
b) An iterative and incremental approach to software development
c) A hybrid approach to software development
d) A waterfall approach to software development
Answer: b) An iterative and incremental approach to software development
1. What is the purpose of Continuous Integration (CI) in Agile?
a) To integrate code changes frequently
b) To test software manually
c) To design software architecture
d) To manage project timelines
Answer: a) To integrate code changes frequently
#SDLC
Overview of the differences between priority and severity in software testing:
Priority vs. Severity
Severity:
Definition: Indicates the impact of a defect on the functionality of the software.
Categories: Critical, Major, Medium, Low.
Determined by: QA engineers.
Purpose: Reflects the seriousness of the defect on the product’s functionality.
Priority:
Definition: Indicates the order in which a defect should be fixed.
Categories: High, Medium, Low.
Determined by: Product managers or stakeholders.
Purpose: Reflects the urgency of fixing the defect based on business needs.
#PriorityandSeverity
Priority vs. Severity
Severity:
Definition: Indicates the impact of a defect on the functionality of the software.
Categories: Critical, Major, Medium, Low.
Determined by: QA engineers.
Purpose: Reflects the seriousness of the defect on the product’s functionality.
Priority:
Definition: Indicates the order in which a defect should be fixed.
Categories: High, Medium, Low.
Determined by: Product managers or stakeholders.
Purpose: Reflects the urgency of fixing the defect based on business needs.
#PriorityandSeverity
Priority and Severity
Here are 20 questions to test your knowledge on priority and severity in software testing:
1.What is the main difference between priority and severity in software testing?
2.Who typically determines the severity of a defect?
3.Who typically determines the priority of a defect?
4.What does a high severity defect indicate?
5.What does a high priority defect indicate?
6.Give an example of a defect with high severity but low priority.
7.Give an example of a defect with low severity but high priority.
8.How many categories of severity are there? Name them.
9.How many categories of priority are there? Name them.
10.Why is it important to differentiate between priority and severity?
11.What type of defect would be classified as ‘Critical’ in severity?
12.What type of defect would be classified as ‘Low’ in priority?
13.Can the priority of a defect change over time? Explain.
14.Can the severity of a defect change over time? Explain.
15.What factors influence the priority of a defect?
16.What factors influence the severity of a defect?
17.Describe a scenario where a defect has high severity and high priority.
18. Describe a scenario where a defect has low severity and low priority.
19.How does the business impact of a defect influence its priority?
20. How does the technical impact of a defect influence its severity?
#PriorityandSeverity
Here are 20 questions to test your knowledge on priority and severity in software testing:
1.What is the main difference between priority and severity in software testing?
2.Who typically determines the severity of a defect?
3.Who typically determines the priority of a defect?
4.What does a high severity defect indicate?
5.What does a high priority defect indicate?
6.Give an example of a defect with high severity but low priority.
7.Give an example of a defect with low severity but high priority.
8.How many categories of severity are there? Name them.
9.How many categories of priority are there? Name them.
10.Why is it important to differentiate between priority and severity?
11.What type of defect would be classified as ‘Critical’ in severity?
12.What type of defect would be classified as ‘Low’ in priority?
13.Can the priority of a defect change over time? Explain.
14.Can the severity of a defect change over time? Explain.
15.What factors influence the priority of a defect?
16.What factors influence the severity of a defect?
17.Describe a scenario where a defect has high severity and high priority.
18. Describe a scenario where a defect has low severity and low priority.
19.How does the business impact of a defect influence its priority?
20. How does the technical impact of a defect influence its severity?
#PriorityandSeverity
You are writing a Postman test script to validate an API response. Which assertion method should you use to check if a specific value exists in the response body? #postman
Anonymous Quiz
35%
pm.test("Response Body Contains", function() {.... })
42%
pm.expect(responseBody).to.include("expectedValue")
23%
pm.response.to.have.property("propertyName","expectedValue")
0%
pm.response.to.be.ok
You are a QA manager overseeing multiple
projects in a DevOps organization. One of your teams wants to adopt Behavior-Driven
Development (BDD) for their testing approach.BWhat is a primary advantage of using BDD in the testing process? By @qa_evaluation
projects in a DevOps organization. One of your teams wants to adopt Behavior-Driven
Development (BDD) for their testing approach.BWhat is a primary advantage of using BDD in the testing process? By @qa_evaluation
Anonymous Quiz
17%
BDD simplifies test automation and reduces theneed for manual testing
66%
BDD encourages collaboration between developers, testers, and non-technical team
17%
BDD eliminates the need for test case Documentation
What is a Thread Group in JMeter?
Anonymous Quiz
67%
A group of virtual users
19%
A group of test cases
7%
A thread-safe variable
8%
A Java class
Your team is debating the balance between automated and manual testing. What logical considerations should guide the decision on when to use automation versus manual testing
Anonymous Quiz
15%
Automate all testing to eliminate the need for manual testing
9%
Rely solely on manual testing for accurate results
74%
Automate repetitive scenarios, reserving manual testing for exploratory testing
2%
Ignore the need for a balance & choose either automation or manual testing
Pin 📍groups links safe and secure
Manual and Automation Testing:
💙 t.me/automation_testing_tools
🤍 https://discord.com/invite/aXzWHphp8H
🌎 manualandautomationtester.blogspot.com
Performance Testing:
💙 t.me/Performance_Testing_Mentor
🤍 https://discord.com/invite/k3KhPgHnC4
Database/ETL Testing:
💙 t.me/Database_testing_mentor
🤍 https://discord.com/invite/dFXMrrw3pW
QA Quiz & Discussion
💙 t.me/qa_evaluation
💙 t.me/qaquiz_discussion
🤍 https://discord.com/invite/utyjMQBP3m
QA - SAP - Developer Jobs Adda Jobs notifications:
💙 Telegram:- t.me/qa_adda
🤍 https://discord.com/invite/JC5u2kJvqG
💚 WhatsApp:- whatsapp.com/channel/0029VaggJG3AYlUDSie8Ze34
Note: Discover best alternative for the telegram user privacy and uses
Manual and Automation Testing:
💙 t.me/automation_testing_tools
🤍 https://discord.com/invite/aXzWHphp8H
🌎 manualandautomationtester.blogspot.com
Performance Testing:
💙 t.me/Performance_Testing_Mentor
🤍 https://discord.com/invite/k3KhPgHnC4
Database/ETL Testing:
💙 t.me/Database_testing_mentor
🤍 https://discord.com/invite/dFXMrrw3pW
QA Quiz & Discussion
💙 t.me/qa_evaluation
💙 t.me/qaquiz_discussion
🤍 https://discord.com/invite/utyjMQBP3m
QA - SAP - Developer Jobs Adda Jobs notifications:
💙 Telegram:- t.me/qa_adda
🤍 https://discord.com/invite/JC5u2kJvqG
💚 WhatsApp:- whatsapp.com/channel/0029VaggJG3AYlUDSie8Ze34
Note: Discover best alternative for the telegram user privacy and uses
👍1