Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Note: I am sure , I know about unit tests and test pyramid in general :). The question is more about end to end tests which are generally long as they are well end to end , covering an business flow/transaction so how ppl test them without running again and again .What are best practices ppl follow/discovered to debug/ update/fixing of them to save debug/update time in maintenance.I used the word 'unit test' in the sense how do you test them in parts or some other faster way.

Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Note: I am sure , I know about unit tests and test pyramid in general :). The question is more about end to end tests which are generally long as they are well end to end , covering an business flow/transaction so how ppl test them without running again and again .What are best practices ppl follow/discovered to debug/ update/fixing of them to save debug/update time in maintenance.I used the word 'unit test' in the sense how do you test them in parts or some other faster way.

Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Note: I am sure , I know about unit tests and test pyramid in general :). The question is more about end to end tests which are generally long as they are well end to end , covering an business flow/transaction so how ppl test them without running again and again .What are best practices ppl follow/discovered to debug/ update/fixing of them to save time in execution.I used the word 'unit test' in the sense how do you test them in parts or some other faster way.

Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Note: I am sure , I know about unit tests and test pyramid in general :). The question is more about end to end tests which are generally long as they are well end to end , covering an business flow/transaction so how ppl test them without running again and again .What are best practices ppl follow/discovered to debug/ update/fixing of them to save debug/update time in maintenance.I used the word 'unit test' in the sense how do you test them in parts or some other faster way.

Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Background: In the long end to end UI automated tests, one needs to execute multiple times during initial scripting/debugging and later for maintenance/fixing which takes a lot of time as a test might be navigating through multiple pages to complete a user journey/transaction.

Problem statement: Is there a way where one can short-circuit these long executions and quickly "test" these tests for some small fix/change in a faster way like sub-tests/unit tests?

Note: I am sure , I know about unit tests and test pyramid in general :). The question is more about end to end tests which are generally long as they are well end to end , covering an business flow/transaction so how ppl test them without running again and again .What are best practices ppl follow/discovered to debug/ update/fixing of them to save time in execution.I used the word 'unit test' in the sense how do you test them in parts or some other faster way.