Test cases are used to systematically test software and verify requirements. A test case contains a set of steps, expected results, and actual results. It has a name, description, prerequisites, and test data. Each test case contains multiple test steps that verify a discrete action. Best practices for writing test cases include avoiding jargon, writing steps independently, and focusing on positive scenarios. Test cases are organized into templates with required fields and naming conventions to facilitate management in testing tools.
Effective Software Test Case Design Approach highlights typical wrong approaches to software test case design and focuses on an effective methodology in test case design from a collaborative approach.
Through the use of an example requirement/user story, this presentation highlights the "interactions" between the stakeholders, i.e. Product Owner, Developer, and Test Engineer in the development of user story acceptance criteria, details, test scope, and effective, consistent and valid test cases.
Now to answer, “What is Testing?” we can go by the famous definition of Myers, which says, “Testing is the process of executing a program with the intent of finding errors”
Here are the preparation slides for chapter 1 from ISTQB Foundation Level Certification syllabus. Hope it is useful.
Here is link to my complete course ISTQB - Foundation Level Certification (CTFL) Training Udemy with 40% discount.
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/?couponCode=SAGARREF
Coupon code: SAGARREF
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
Test Automation Best Practices (with SOA test approach)Leonard Fingerman
Today we hear a lot of buzz about the latest & greatest test automation tools like Selenium, Rational Functional Tester or HP LoadRunner but to make your test automation effort successful it might take more than just having the right tool. This presentation will try to uncover major pitfalls typically involved with test automation efforts. It will provide guidance on successful strategy as well as differences among third-generation frameworks like keyword-driven, data-driven and hybrid. It will also cover various aspects of SOA test automation
This is the presentation describing different techniques used to write test cases for software testing. You can have overview with detailed example for test case techniques. After reading this, You'll able to assume which technique can be more useful to you software testing.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Effective Software Test Case Design Approach highlights typical wrong approaches to software test case design and focuses on an effective methodology in test case design from a collaborative approach.
Through the use of an example requirement/user story, this presentation highlights the "interactions" between the stakeholders, i.e. Product Owner, Developer, and Test Engineer in the development of user story acceptance criteria, details, test scope, and effective, consistent and valid test cases.
Now to answer, “What is Testing?” we can go by the famous definition of Myers, which says, “Testing is the process of executing a program with the intent of finding errors”
Here are the preparation slides for chapter 1 from ISTQB Foundation Level Certification syllabus. Hope it is useful.
Here is link to my complete course ISTQB - Foundation Level Certification (CTFL) Training Udemy with 40% discount.
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/?couponCode=SAGARREF
Coupon code: SAGARREF
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
Test Automation Best Practices (with SOA test approach)Leonard Fingerman
Today we hear a lot of buzz about the latest & greatest test automation tools like Selenium, Rational Functional Tester or HP LoadRunner but to make your test automation effort successful it might take more than just having the right tool. This presentation will try to uncover major pitfalls typically involved with test automation efforts. It will provide guidance on successful strategy as well as differences among third-generation frameworks like keyword-driven, data-driven and hybrid. It will also cover various aspects of SOA test automation
This is the presentation describing different techniques used to write test cases for software testing. You can have overview with detailed example for test case techniques. After reading this, You'll able to assume which technique can be more useful to you software testing.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
For Youtube Videos: bit.do/sevents
What is a testing technique?
Black and White box testing
Black box test techniques
White box test techniques
Error Guessing
Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings.
Want to know the case for Test-Driven Development? Want to know style tips and gotchas for Testing and TDD? Let Alex Chaffee, former Mad Scientist at Pivotal Labs, tell you everything you didn't know you didn't know about testing.
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...KarenMiner
Are you searching for solved questions for Microsoft Querying Data with Transact-SQL 70-761. You also need to pass it in first attempt but It is difficult to pass Microsoft 70-761 for most of the students. You can make it easier with the help of fravo Microsoft 70-761 Querying Data with Transact-SQL Exam dumps. Get complete version here:
https://www.fravo.com/70-761-exams.html
3. Definition – Test Case What is a Test Case? Definition 1 A set of test steps, execution conditions and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Definition 2 Test cases are specific inputs and procedures that you will follow when you test software. Analogy A Test Case is like a recipe. You follow the steps to produce an end result.
4. Basic Parts of a Test Case A Test Case is multiple Steps which are comprised of these 4 basics parts: Description of the Test Case Verify that the text is blue. Description of each Step Locate text in first paragraph Expected result each Step The text should be blue Actual result each Step The text is blue
5. Test Step A Test Step is the smallest portion of a Test Case. It typically describes a single action in a chain of actions which go on to comprise a Test Case: Usually start with a verb such as: Verify, Validate, Navigate Usually are doing something very discrete. Validate color, Verify SSN, Navigate to account Examples: Step 1. Navigate to SSN field. Step 2. Enter a valid ID. Step 3. Validate that the SSN field will only accept a 9 digit number
23. Best Practices When writing: Avoid lingo (words, abbreviations, acronyms and phrases used in your department or field) The customer will be using ABF financing. The customer will be using Asset Based Financing. Write the case as if you are not going to be executing it. Report should look like Bettys report. Output should be TPS 123 report. Write Test Cases so they Test a limited set of functionality. Verify that all Deposits work in Alnova. Execute a deposit in Alnova.
24. Example Test Case with Steps For existing consumer and commercial accounts, add an alternative contact address for a statement address using this mailing address: 123 Maple Street, Birmingham, AL Test Case: Open an existing consumer account: Test Step 1. In business object, enter last name of customer Test Step 2. Choose Add an Address Test Step 3. Enter 123 Maple Street Test Step 4. Etc….
30. Description – Brief description of the event that you are testing Example RET_CONSREG_001_Register a Customer This means Retail Department – Registering a Consumer – Incremental number - Scenario Description * 001 is the scenario number and is the number used in the Test Case naming convention
31.
32. Type = Use an abbreviation of the type of transaction that allows you to best identify the Test Scenario
34. Test Case Number – Incremental Number (May have multiple Test Cases per Test Scenario)
35. Description – Brief description of the event that you are testingExample CM_NCONMAINT_001_002_Register a Customer This means Commercial Department – Non-Consumer Maintenance – Test Scenario number– Test Case Number – Test Case Description
36. Scenario Applied to Test Cases How Scenarios Can be Used for Your Test Cases
49. All following cells (in the rows below the first line) must be blank except the design steps (Step Name, Description – Design Steps, Expected– Design Steps)
50. Remove Blank rows between tests (they will not be accepted by ALM)*Pre-Requisites = items (non-data) required to perform the test such as hardware, environment needs, batches (example: ATM cards) *Test Data = data required to perform the test (example: valid account information)
51.
52. Subject on the first row of every test case must have the path to the upload destination. For example: UAT/Rel 1.0/RET for Retail
53. Test Name - can not exceed 40 characters - Manually correct
54. Description - can not have any unique characters such as , : ; ‘ < () / ^ " * Manually remove any unique characters before uploading
55. Description - can have an underscore or a period (_ . ) along with numbers and letters
56. Description, Pre-Requisites, or Test Data – if these fields on the first row of a test case are blank, enter TBD in the field/s – Add these if possible or TBD
57. Test Attributes - for UAT test cases must say “User Acceptance Test”
58. Test priority - must be either A (high), B (medium) or C (low)
65. Sharepoint Link to UAT Naming Conventions http://projectdocuments.compassbnk.com/platformupgrade/Core/Forms/AllItems.aspx?RootFolder=%2fplatformupgrade%2fCore%2fTest%20Coordination%2fR1%2fUAT%2fUAT%20%2d%20R1%20%2d%20UAT%20Tester%27s%20Area&View=%7b047D9B21%2dA186%2d40D5%2dB21F%2d406DD2C061CA%7d