added csharp cookie code

[rpallavisharma]

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

added csharp cookie code

Motivation and Context

example was added

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

enhancement, documentation

---

Description

• Added a new C# test class CookiesTest with methods to demonstrate cookie operations using Selenium WebDriver.
• Methods include adding, retrieving, and deleting cookies, showcasing practical examples of cookie management.
• Updated documentation across multiple languages (English, Japanese, Portuguese, Chinese) to reference the new C# code examples using gh-codeblock.
• Improved the maintainability of the documentation by linking to code files instead of embedding code directly.

---

Changes walkthrough 📝

	Relevant files
Enhancement	CookiesTest.cs Add C# examples for cookie operations in Selenium                examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs Added license information and necessary imports. Implemented multiple test methods for cookie operations. Methods include adding, retrieving, and deleting cookies. Utilized ChromeDriver for browser interactions. +97/-5
Documentation	cookies.en.md Update English documentation to reference C# code examples website_and_docs/content/documentation/webdriver/interactions/cookies.en.md Replaced inline C# code examples with references to code file. Updated documentation to use gh-codeblock for C# examples. +10/-113 cookies.ja.md Update Japanese documentation to reference C# code examples website_and_docs/content/documentation/webdriver/interactions/cookies.ja.md Replaced inline C# code examples with references to code file. Updated documentation to use gh-codeblock for C# examples. +10/-113 cookies.pt-br.md Update Portuguese documentation to reference C# code examples website_and_docs/content/documentation/webdriver/interactions/cookies.pt-br.md Replaced inline C# code examples with references to code file. Updated documentation to use gh-codeblock for C# examples. +10/-113 cookies.zh-cn.md Update Chinese documentation to reference C# code examples website_and_docs/content/documentation/webdriver/interactions/cookies.zh-cn.md Replaced inline C# code examples with references to code file. Updated documentation to use gh-codeblock for C# examples. +10/-113

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	cbaabb5

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Resource Management The WebDriver instance is not properly disposed of in the test methods. Consider using a 'using' statement or implementing IDisposable to ensure proper cleanup of resources. Test Isolation The WebDriver instance is shared across all test methods, which could lead to state bleeding between tests. Consider creating a new WebDriver instance for each test method to ensure proper isolation. Error Handling There is no error handling or assertions in some of the test methods. Consider adding appropriate try-catch blocks and assertions to ensure the tests are robust and informative.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Implement proper test setup and teardown methods for better test isolation and resource management Consider using a setup method to initialize the WebDriver before each test, and a teardown method to quit the driver after each test. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [28-36] -WebDriver driver = new ChromeDriver(); +private IWebDriver driver; -[TestMethod] -public void addCookie(){ - driver.Url="https://www.selenium.dev/selenium/web/blank.html"; - // Add cookie into current browser context - driver.Manage().Cookies.AddCookie(new Cookie("key", "value")); +[TestInitialize] +public void SetUp() +{ + driver = new ChromeDriver(); +} + +[TestCleanup] +public void TearDown() +{ driver.Quit(); } +[TestMethod] +public void AddCookie() +{ + driver.Url = "https://www.selenium.dev/selenium/web/blank.html"; + // Add cookie into current browser context + driver.Manage().Cookies.AddCookie(new Cookie("key", "value")); +} + Apply this suggestion Suggestion importance[1-10]: 9 Why: Implementing setup and teardown methods improves test isolation, ensures consistent WebDriver initialization and cleanup, and follows best practices for unit testing.	9
	Implement proper resource management for WebDriver instances Use using statements for IWebDriver to ensure proper resource disposal. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [28] -WebDriver driver = new ChromeDriver(); +using (IWebDriver driver = new ChromeDriver()) +{ + // Test code here +} Apply this suggestion Suggestion importance[1-10]: 8 Why: Using 'using' statements ensures proper disposal of IWebDriver resources, preventing potential memory leaks and improving overall resource management.	8
Enhancement	Add assertions to verify the expected outcomes of cookie operations Add assertions to verify the expected outcomes of cookie operations. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [31-36] -public void addCookie(){ - driver.Url="https://www.selenium.dev/selenium/web/blank.html"; +public void AddCookie_ShouldAddCookieToCurrentBrowserContext() +{ + driver.Url = "https://www.selenium.dev/selenium/web/blank.html"; // Add cookie into current browser context driver.Manage().Cookies.AddCookie(new Cookie("key", "value")); - driver.Quit(); + + // Verify the cookie was added + var cookie = driver.Manage().Cookies.GetCookieNamed("key"); + Assert.IsNotNull(cookie, "Cookie should not be null"); + Assert.AreEqual("value", cookie.Value, "Cookie value should match"); } Apply this suggestion Suggestion importance[1-10]: 9 Why: Adding assertions verifies the expected outcomes of cookie operations, significantly improving the test's effectiveness and reliability.	9
	Improve test method naming for better clarity and consistency Use more descriptive test method names that follow a consistent naming convention. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [31] -public void addCookie(){ +public void AddCookie_ShouldAddCookieToCurrentBrowserContext() Apply this suggestion Suggestion importance[1-10]: 6 Why: More descriptive and consistent test method names enhance code readability and make the purpose of each test clearer, improving maintainability.	6

💡 Need additional feedback ? start a PR chat

[harsha509]

Comment needs to be changed accordingly to .net bindings !

[rpallavisharma]

sorry , will modify this

[harsha509]

Duplicate of #2049!