New pages
Jump to navigation
Jump to search
- 08:44, 5 June 2025 Testing Techniques (hist | edit) [216 bytes] Alexey Shirin (talk | contribs) (Created page with "Exploratory Testing Regression Testing Smoke Testing Sanity Check (Re-test) Checklist Testing Test Case Testing")
- 08:37, 5 June 2025 Test Case (hist | edit) [1,936 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''What Is a Test Case & How to Write Good Test Cases – Basic Guide''' === '''What Is a Test Case?''' A test case is a '''documented set of actions''' used to check if a specific part of the system works correctly. Each test case focuses on a single objective and includes clear input, steps to perform, and the expected result. Test cases help testers work consistently, avoid missing checks, and make it easy to repeat tests later. '''Why Are Test Cases Important?'...") Tag: Visual edit
- 08:33, 5 June 2025 Test Case Testing (hist | edit) [1,593 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Test Case Based Testing – Basic Guide''' === '''What is Test Case Testing?''' Test case testing means executing '''pre-created test cases''' that describe exactly what to test, how to test it, and what results are expected. This method helps ensure '''repeatability, traceability, and coverage'''. It is often used in formal test cycles like regression, system, or acceptance testing. '''How to Prepare?''' Review the assigned test cases in your test management t...") Tag: Visual edit
- 08:28, 5 June 2025 Checklist Testing (hist | edit) [1,404 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Checklist Testing – Basic Guide''' === '''What is Checklist Testing?''' Checklist testing means performing tests using a '''predefined list of conditions or items to verify'''. It is less formal than test cases but still structured. The checklist helps ensure that important features, actions, or rules are not forgotten during testing. '''How to Prepare?''' Use an existing checklist provided by your team or test lead, or build one based on product requirements...") Tag: Visual edit
- 08:27, 5 June 2025 Sanity Check (Re-test) (hist | edit) [1,303 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Sanity Testing – Basic Guide (Re-test Fixed Bugs)''' === '''What is Sanity Testing?''' Sanity testing checks that specific bugs or issues reported earlier are now fixed and working as expected. It is focused and limited in scope — not a full test cycle. The goal is to quickly verify that fixes were successful. '''How to Prepare?''' Review the list of fixed bugs from the issue tracker (e.g. Jira, Redmine). Read each bug report carefully: understand the probl...") Tag: Visual edit
- 08:25, 5 June 2025 Smoke Testing (hist | edit) [1,253 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Smoke Testing for Web Sites – Basic Guide''' === '''What is Smoke Testing?''' Smoke testing is a quick check to make sure the website is up and major functions are working after a new build or deployment. It does '''not''' cover deep or detailed testing — just the basic “is it working at all” check. '''How to Prepare?''' Identify the '''critical paths''' of the website — core features that must work for the product to be usable (e.g. homepage loads, l...") Tag: Visual edit
- 08:24, 5 June 2025 Regression Testing (hist | edit) [1,373 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Regression Testing for Web Sites – Basic Guide''' === '''What is Regression Testing?''' Regression testing means re-testing existing features to make sure that recent changes (new features, bug fixes, config updates) did not break anything that worked before. It is usually done before release, or after code changes. '''How to Prepare?''' Use a '''predefined test suite''' – a list of important test cases that cover core features. These should include both fu...") Tag: Visual edit
- 08:22, 5 June 2025 Exploratory Testing (hist | edit) [1,614 bytes] Alexey Shirin (talk | contribs) (Created page with "=== '''Exploratory Testing for Web Sites – Basic Guide''' === '''What is Exploratory Testing?''' Exploratory testing is a hands-on testing approach where testers actively explore the website without using predefined test cases. The goal is to find unexpected issues by thinking like a user. Testers design and run tests at the same time, based on what they learn during testing. '''How to Prepare?''' Before testing, understand the product’s purpose, main user flows,...") Tag: Visual edit
- 08:22, 5 June 2025 Testing Technics (hist | edit) [0 bytes] Alexey Shirin (talk | contribs) (Created page with "Exploratory Testing Regression Testing Smoke Testing Sanity Check (Re-test) Checklist Testing Test Case Testing") Tag: Visual edit
- 20:49, 15 May 2025 Phone system RingCentral (hist | edit) [4,489 bytes] Sergey Ershov (talk | contribs) (Created page with "{| class="wikitable" |'''Reference Docs/ File''' |'''Shortcut link''' |- |Support |https://support.ringcentral.com/ |- | | |- |RingCX |https://ringcx.ringcentral.com/ |- |REx Admin Portal |[https://ringcx.ringcentral.com/ https://service.ringcentral.com] |- | | |- |Project Google Drive Folder |https://drive.google.com/drive/folders/14GLRH8zC4CmnHj9Vu5Gfgs8dVm-MZBv8?usp=sharing |- |RingCentral University |https://university.ringcentral.com/ |- |RCx Trainings |https://univ...") Tag: Visual edit