added csharp cookie code

[pallavigitwork]

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

added csharp cookie code

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 to manage cookies using Selenium WebDriver.
• Implemented methods for adding, retrieving, and deleting cookies, with assertions to verify operations.
• Updated documentation across multiple languages to reference the new C# test class, improving the structure and clarity of C# examples.

---

Changes walkthrough 📝

	Relevant files
Enhancement	CookiesTest.cs Add C# tests for cookie management in Selenium                      examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs Added a new C# test class CookiesTest for cookie interactions. Implemented methods to add, retrieve, and delete cookies. Utilized WebDriver to manage cookies in browser context. Included assertions to verify cookie operations. +97/-5
Documentation	cookies.en.md Update C# cookie examples in documentation                              website_and_docs/content/documentation/webdriver/interactions/cookies.en.md Updated C# code examples to reference new test class. Replaced inline code with links to the new C# test class. Improved documentation structure for C# examples. +10/-113 cookies.ja.md Update C# cookie examples in Japanese documentation            website_and_docs/content/documentation/webdriver/interactions/cookies.ja.md Updated C# code examples to reference new test class. Replaced inline code with links to the new C# test class. Improved documentation structure for C# examples. +10/-113 cookies.pt-br.md Update C# cookie examples in Portuguese documentation        website_and_docs/content/documentation/webdriver/interactions/cookies.pt-br.md Updated C# code examples to reference new test class. Replaced inline code with links to the new C# test class. Improved documentation structure for C# examples. +10/-113 cookies.zh-cn.md Update C# cookie examples in Chinese documentation              website_and_docs/content/documentation/webdriver/interactions/cookies.zh-cn.md Updated C# code examples to reference new test class. Replaced inline code with links to the new C# test class. Improved documentation structure 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	fd1ae78

[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 resource cleanup. Test Isolation The WebDriver instance is shared across all test methods, which could lead to state pollution between tests. Consider creating a new WebDriver instance for each test method. Error Handling There's no error handling or assertions to verify that cookie operations are successful. Consider adding try-catch blocks and appropriate assertions.

[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 resource management and test isolation Use a setup method with [TestInitialize] attribute to initialize the WebDriver before each test, and a teardown method with [TestCleanup] attribute to quit the driver after each test. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [28-35] -WebDriver driver = new ChromeDriver(); +private WebDriver 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: Using TestInitialize and TestCleanup methods improves test isolation, ensures consistent setup and teardown for each test, and centralizes WebDriver management, reducing code duplication and potential resource leaks.	9
	Ensure proper resource management and disposal of WebDriver instances Implement IDisposable interface and use 'using' statement to ensure proper disposal of WebDriver resources. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [28] -WebDriver driver = new ChromeDriver(); +using (WebDriver driver = new ChromeDriver()) +{ + // Test code here +} Apply this suggestion Suggestion importance[1-10]: 8 Why: Implementing IDisposable and using 'using' statements ensures proper cleanup of WebDriver resources, preventing potential memory leaks and improving overall resource management.	8
	Improve method naming consistency and adherence to C# conventions Use more descriptive and consistent method names following C# naming conventions (PascalCase for public methods). examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [31-91] -public void addCookie(){ -public void getNamedCookie(){ -public void getAllCookies(){ -public void deleteCookieNamed(){ -public void deleteCookieObject(){ -public void deleteAllCookies(){ +public void AddCookie() +public void GetNamedCookie() +public void GetAllCookies() +public void DeleteCookieNamed() +public void DeleteCookieObject() +public void DeleteAllCookies() Apply this suggestion Suggestion importance[1-10]: 6 Why: Consistent and proper method naming improves code readability and maintainability, and adheres to C# best practices, making the code more professional and easier to understand for other developers.	6
Enhancement	Enhance test effectiveness by adding assertions to verify expected outcomes of operations Add assertions to verify the expected outcomes of cookie operations, enhancing the test's effectiveness. examples/dotnet/SeleniumDocs/Interactions/CookiesTest.cs [31-35] -public void addCookie(){ - driver.Url="https://www.selenium.dev/selenium/web/blank.html"; +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")); - driver.Quit(); + + // Verify the cookie was added + Cookie addedCookie = driver.Manage().Cookies.GetCookieNamed("key"); + Assert.IsNotNull(addedCookie, "Cookie should not be null"); + Assert.AreEqual("value", addedCookie.Value, "Cookie value should match"); } Apply this suggestion Suggestion importance[1-10]: 7 Why: Adding assertions to verify the outcomes of cookie operations significantly improves the test's effectiveness by ensuring that the expected behavior is actually occurring, rather than just executing the operations without validation.	7

💡 Need additional feedback ? start a PR chat

[harsha509]

Thank you @pallavigitwork !