I am running python on a Mac (10.15.6). When I run this script from the terminal, it works fine
from selenium import webdriver
But starting it from the Python IDLE or VSCode, I get the message:
ModuleNotFoundError: No module named 'selenium'
I have no clue why it works from the terminal and not from the shell. It would be great if someone could help me out or point me in a direction where I might find the answer 
With TestNG you can define your scenarios in testsuites (a group of related tests) in xml files. For example, we have a folder for each Scrum sprint, and in them we place one file for each User Story.
<?xml version="1.0" encoding="UTF-8"?>
<!-- US XX: As an user I want to access to the intranet with a login form in order to access to private resources -->
<suite name="IntranetLogin" enabled="true">
<test name="LoginChecking" order-by-instances="true">
<classes>
<class name="com.company.LoginTestSet" />
<methods>
<include name="loginWithExistingUser" />
<include name="loginWithNonExistingUser" />
<include name="loginWithWrongPassword" />
<include name="loginWithBlockedUser" />
<include name="loginWithEmptyFields" />
</methods>
</classes>
</test>
...
</suite>
You can define the tests steps in the javadoc of each test method so they will appear in the html documentation that is auto generated when you compile. For example:
/**
* Description: Should display an error if the user try to log in with an incorrect password
*
* Test steps:
* 1) Go to the login page
* 2) Write an username
* 3) Write an incorrect password
* 4) Click on Submit button
*
* Expected results:
* - An error message is displayed
* - The browser remains in the login page
* */
And if you want a more expressive way to write the test steps you can take a look at Doxygen.
Has anyone tested benchmarks on performance difference between using the new css feature content-visibility: auto in Chrome 85 compared to other lazy loading methods? Is it worth switching over current lazy loading using JavaScript to using CSS content-visibility: auto?
We have a very large application with nearly 2K testcases for regression. Our process is multiple sprints of work towards a single release. So, we use a dedicated regression test plan.
My question is how to manage regression runs? Right now, we clone the Master Regression suite or prior regression suite. This allows us to preserve the previous regression results. But this method creates new unique test cases, which doesn't keep associated bugs.
If we reset all the tests in the current suite, I know the previous runs could be seen at the test case level. However, I can't figure out how to call up historical aggregate results, for a previous run.
How should DevOps be used for managing repeat test runs?
What ever you did it looks like right But I have not seen Boundary Value testing points in it
What is Equivalent Class Partitioning? Equivalent Class Partitioning is a black box technique (code is not visible to tester) which can be applied to all levels of testing like unit, integration, system, etc. In this technique, you divide the set of test condition into a partition that can be considered the same.
What is Boundary Testing? Boundary testing is the process of testing between extreme ends or boundaries between partitions of the input values.
Why Equivalence & Boundary Analysis Testing This testing is used to reduce a very large number of test cases to manageable chunks. Very clear guidelines on determining test cases without compromising on the effectiveness of testing. Appropriate for calculation-intensive applications with a large number of variables/inputs
Summary:
Can someone share a general check list for testing usual android and ios application?