TestAny.Essentials.Api
1.0.5.11
See the version list below for details.
dotnet add package TestAny.Essentials.Api --version 1.0.5.11
NuGet\Install-Package TestAny.Essentials.Api -Version 1.0.5.11
<PackageReference Include="TestAny.Essentials.Api" Version="1.0.5.11" />
paket add TestAny.Essentials.Api --version 1.0.5.11
#r "nuget: TestAny.Essentials.Api, 1.0.5.11"
// Install TestAny.Essentials.Api as a Cake Addin
#addin nuget:?package=TestAny.Essentials.Api&version=1.0.5.11
// Install TestAny.Essentials.Api as a Cake Tool
#tool nuget:?package=TestAny.Essentials.Api&version=1.0.5.11
Build your Api test easily with few simple steps and this framework allows you to focus more on your Test. The wrapper allows to call the endpoints easily and provide different options on your request and response.
Overview
This framework is build as part of Selenium Essentials to provide a Api framework which allows to make calls to endpoint easily.
- Api framework to write integration tests
-- Supports fluent way of endpoint definitions
-- Support most of the operations
-- Simple and easy to manage the tests
Example,
return new TestApiHttp()
.SetEnvironment("http://api.openweathermap.org/")
.PrepareRequest("/data/2.5/forecase")
.Get()
.ResponseBody
.ContentJson;
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- HtmlAgilityPack (>= 1.11.46)
- Pj.Library (>= 1.0.4.11)
- Pj.Library.Secure (>= 1.0.4.11)
- Pj.Library.ThirdParty (>= 1.0.4.11)
- TestAny.Essentials.Core (>= 1.0.5.11)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on TestAny.Essentials.Api:
Package | Downloads |
---|---|
Selenium.Essentials
Build Selenium web automation test using advanced web controls with wrappers and plenty of extensions to fasten your automation development time. Focus more on script logic with better consistent script execution, less maintenance, no hardwaits, with improved script execution performance and integrated Api testing framework. Overview Selenium provides only option to create only a single generic control which is called the IWebElement. Imagine if you have option to declare controls which resemble the html elements and provide its functionality, for example, Checkbox, Textbox, Button. Selenium Essentials provide new custom controls giving meaning to your page objects and making it more readable. Every control is defined from a BaseControl which has a set of definitions applicable to all controls as well as its custom actions. For example, Checkbox control will have all properties of the BaseControl and also defines Check() which ticks the checkbox in the UI, UnCheck() which unticks the checkbox, IsChecked returns a bool value based on the control is Checked or Unchecked reading from the UI. The Custom control also expose the underlying IWebElement as a property used by Selenium, in case you need to do any operations on top of this. There are plenty of Wait operation defined on the base control which flows through all the custom controls. There are different overrides to the wait operation where you can control the time to wait, whether to throw exception if fails, message for assertions when the waits are used for assert operations. Some custom control overrides the default wait to give a better meaning. Read more about controls here WebDriver and WebElement comes with some useful extensions which helps during the automation. For example, executing javascript, scroll operations, taking screenshot, getting driver capabilities. There is a simple Api framework, which can help in writing Integration tests using a fluent approach. Package contains lots of extensions and helpers over different types which will help increase productivity. Example, - Loading excel and converting to C# - Converting Json to Dictionary - Serialization and Deserialization - Regular Expression, DateTime, String, Enumerable, Async Benefits - Readable page objects which clearly defines what each control resemble in the browser - Custom controls with wrapped operations -- Checkbox - Check, UnCheck, IsChecked, more -- Textbox - Custom clear and set operations (extented clear which will make sure the content is cleared by doing Ctrl+a and BackSpace) and Set operation to overcome some responsive issues -- UnorderedList - Total, Items -- Select - operations on SelectElement -- Table - TotalColumns, TotalRows, ColumnNames, GeCellContent, GetRowPosition, GetColumnPosition, more -- Collection - working with Driver.FindElements(...) -- FileUpload - UploadFile -- Button -- WebControl - for all generic html control - WebElement and WebDriver extension methods for most of the - Api framework to write integration tests -- Supports fluent -- Support most of the operations -- Simple and easy to manage the tests - Extensions which provide many methods for automation engineering works -- String, RegEx, Enumerable, DatTime, Async, more - Helpers to load excel, serialization, Json to Dictonary, more - Attributes for test to load json and xml data |
|
Jira.Rest.Sdk
Jira.Rest.Sdk ======== SDK using Jira REST to query Jira application using Rest endpoints. Manage your Jira process from query, create and update issues. Integrate with you existing automation solution or process that will manage both Jira Server and Cloud based application. The request and response objects are having proper DTOS (data transfer or model objects) defined within this package. How to use: ```C# //Connect to cloud hosted Jira service var jiraService = new JiraService("jira url", "username", "password", isCloudVersion: true); //Connect to cloud hosted Jira service var jiraService = new JiraService("jira url", "username", "password", isCloudVersion: false); //Get a test case by Key var issue = jiraService.IssueGetById("POC-100"); //Get a list of issues matching your jql var issue = jiraService.IssueSearch("<your jql>"); //Get project by custom filters on any properties var project = jiraService.ProjectsGet(p => p.Name.EqualsIgnoreCase("poc")).FirstOrDefault(); //Create a Issue var newIssue = jiraService.IssueCreate(projectKey: "POC", issueType: "Story", summary: "Build new interface for model B", description: "Provide your detailed description for the issue", priority: "High", parentKey: "POC-99") ``` |
|
ZephyrScale.Rest.Sdk
SDK to connect to the Zephyr Scale app using Zephyr Scale's Rest endpoints. Manage your communication and easily retrieve and publish test cases, test cycle and execution results to Zephyr Scale. You can integrate with you existing automation solution or process that will manage these process. Support both Server and Cloud hosted Zephyr Scale application. For more information on Cloud: https://support.smartbear.com/zephyr-scale-cloud/api-docs/ For more information on Server: https://support.smartbear.com/zephyr-scale-server/api-docs/v1/ The request and response objects are having proper DTOS (data transfer or model objects) defined within this package. How to use: //Connect to cloud hosted Zephyr Scale service var zService = new ZephyrScaleCloudService("app url", "user api token"); //Connect to server hosted Zephyr Scale service var zService = new ZephyrScaleOnPremService("app url", "username", "password"); //Get a test case by Key var testCase = zService.TestCasesGet("POC-T1"); //Create a new Test case var newTestCase = ZephyrOnPremService.TestCaseCreate(new TestCaseCreateRequest { ProjectKey = "PCO", Folder = "/Automation", Name = "Verify the integration between app and zyphr", IssueLinks = new[] { "PCO-1432", "PCO-23" }.ToList(), Owner = "peterjoseph", Labels = new[] { "Automation", "Integration", "Api" }.ToList(), Status = "Approved" }); |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.6 | 112 | 5/1/2024 |
1.0.5.28 | 421 | 3/10/2024 |
1.0.5.27 | 294 | 3/10/2024 |
1.0.5.26 | 1,427 | 11/22/2023 |
1.0.5.25 | 1,099 | 10/18/2023 |
1.0.5.24 | 914 | 10/17/2023 |
1.0.5.23 | 909 | 10/17/2023 |
1.0.5.22 | 1,016 | 10/16/2023 |
1.0.5.21 | 908 | 10/16/2023 |
1.0.5.20 | 931 | 10/13/2023 |
1.0.5.19 | 1,124 | 10/11/2023 |
1.0.5.18 | 1,007 | 10/10/2023 |
1.0.5.17 | 1,189 | 9/29/2023 |
1.0.5.16 | 1,210 | 9/6/2023 |
1.0.5.15 | 2,633 | 2/14/2023 |
1.0.5.14 | 3,012 | 11/21/2022 |
1.0.5.13 | 2,119 | 11/20/2022 |
1.0.5.12 | 2,217 | 11/15/2022 |
1.0.5.11 | 1,955 | 10/16/2022 |
1.0.5.10 | 2,418 | 9/1/2022 |
1.0.5.9 | 1,983 | 8/7/2022 |
1.0.5.8 | 4,200 | 5/25/2022 |
1.0.5.7 | 1,721 | 4/20/2022 |
1.0.5.6 | 7,649 | 4/12/2022 |
1.0.5.5 | 2,013 | 4/6/2022 |
1.0.5.4 | 1,925 | 4/5/2022 |
1.0.5.3 | 1,994 | 4/4/2022 |
1.0.5.2 | 2,108 | 3/20/2022 |
1.0.5.1 | 1,992 | 1/9/2022 |
1.0.5 | 1,649 | 12/31/2021 |
Release 1.0.5.9
- Retry on every action [Get, Post, Delete, Put] has now additional parameter to control the timeout error from server. retryOnRequestTimeout, can be set to true/false to fail when the request timeout or to retry
- AddingCookies is renamed to AddCookies under TestApiRequest
- Option to control
-- Set Timeout
-- Auto Redirection on the server for a request
-- Extract Domain cookies
-- No Cache
Release 1.0.5.4
- Api Request can now accept SetQueryParameter and SetJsonBody with any object passed
Release 1.0.5.2
- Api Retry option now has ability to control on which httpstatuscode the retry should occur
Release 1.0.5.2
- Introduce Api framework with PUT PATCH commands
-- WithRetry option with time on interval
-- Response contains cookies extracted from domains
-- Cookie extension to merge and contact cookies
-- Introducing Proxy for API request based on the user data
-- Introducing Certificates to be passed on the request
-- Response has more request details from headers to cookies
- Tests are now upgraded to .NET 6
Release 1.0.5.1
- Bug fix when loading ApiResponse as HtmlContent
Release 1.0.5
- Introduce TestAny.Essentials.Core
- Introduce TestAny.Essentials.Api. All Api related functionality are moved into this new package
- There are some breaking changes
-- SeAppConfig is renamed to TestAnyAppConfig
-- TestAnyAppConfig is now moved into TestAny.Essentials.Core
-- TestContextHelper is renamed to TestAnyTestContextHelper
-- TestAnyTestContextHelper is now moved into TestAny.Essentials.Core
-- Dtos models are now moved into the Core project
Release 1.0.4
- Introduction of Selenium.Essentials.Api for Api testing
- Usage of utilities from Pj.Library
- Remove Utility class from Selenium Essentials
- Move properties from Utility class to SeAppConfig class
- Move InitializeFramework(..) from Utility to SeAppConfig class