We can automate the functional testing, regression testing and performance testing.

Regards,

Kavita

Captchas breaking of Google (ReCaptcha-2 and ReCaptcha-3), Facebook, BitFinex, Bing, Hotmail, SolveMedia, Yandex,
and more than 12000 another size-types of captchas,
with highest precision (80..100%) and highest speed (100 img per second).
You can use XEvil 5.0 with any most popular SEO/SMM software: iMacros, XRumer, SERP Parser, GSA SER, RankerX, ZennoPoster, Scrapebox, Senuke, FaucetCollector and more than 100 of other programms.

Interested? There are a lot of impessive videos about XEvil in YouTube.

FREE DEMO AVAILABLE!

See you later!

Thanks

The answers that you have given were easily understandable and remembrable….

Thanks!
Regards,
Smitha

Nice effort by u.

Thanks

please check my comment also.

severity : how sever the bug affected the software system.(Testing Team)

1-Showstopper System severely impacted/not available – no workaround
2-Critical System available but certain function fails
3-Major Certain function fails with low impact, workaround available
4-Minor Minimal impact on system function, or cosmetic error

priority : Giving preference to severity .. say SEV1 should be done first, SEV2 should be done 2nd etc. (Developer Team)

thanks
venkat
[email protected]

If you are looking for bug tracking tool, then you can go for some open-source tools like Mantis or Bugzilla. They are very easy to understand and use.

Otherwise you can create your own kind of tracking sheet using MS-excel.

Major elements which should present in your tracker are,

Bug ID, Test Case ID, Date of Reporting, Date of Resolved, Summary, Description, Steps-to-reproduce, Assigned to, Status, Severity, Priority and comments.

can you elaborate it..?..

Thank You…

priority is to say how important the bug is to fix.

software testing life cycle is the procedure to test software.
In the software testing life cycle, there are many phases like,
1-Requirements analysis: Requirement analysis refers to the step where the Software Testing Lifecycle begins, In requirement analysis, we analyze the requirement means how to test, whom to test and in this phase, we gather the requirements
2-Test planning: During this phase, the test strategy is outlined in a test plan document. This strategy includes tools needed, testing steps, and roles and responsibilities. Part of determining this strategy is a risk and cost analysis and an estimated timeline for testing.
3-Test environment setup: During this phase, testing environments are configured and deployed. This phase may include a variety of testing tools, including TestComplete, Selenium, Appium, or Katalon Studio. Sometimes, this phase also includes setting up test servers. Once environments are deployed, smoke tests are performed to ensure that environments are working as expected with all intended functionality.
4-Test execution: During this phase, features are tested in the deployed environment, using the established test cases. Expected test results are compared to actual and results are gathered to report back to development teams.
5- Test closure: This is the last phase of the STLC, during which a test result report is prepared. This report should summarize the entire testing process and provide comparisons between expected results and actual. These comparisons include objectives met, time taken, total costs, test coverage, and any defects found.