Test Automation
My experience in writing test automation has revolved around two software tools, Cypress and Selenium Webdriver. I am a student of Javascript which Cypress is written in so when working with Selenium I choose the same coding approach using the Mocha framework and Chai libraries to write test automation. In my linked Github projects I built some simple forms using Bootstrap templates and wrote test automation against them. The testing method should follow the manual test plan.
Github
Postman
Most of my experience with Postman is writing test cases for HTML responses. Writing assertions for status codes, value types, response times, and schema. Using the test runner tool has been very useful to test many API calls manually at once. In my linked Postman collection there are basic test case examples.
Manual Testing
My testing methodology when writing test cases is to test basic UI components in a happy path, there is not a lot of focus on granularity (testing designs or much CSS) just if the components of the web application function or not. Negative test cases are used to check for the intended UI failures within the UI. As edge cases are written to find the unintended UI failures, in my experience there can be a misunderstanding between Edge and Negative test cases, these need to be organized in a way that differentiates both with clear descriptions. Manual test cases are written first with those methods in mind
Azure