登録は簡単!. 無料です
または 登録 あなたのEメールアドレスで登録
AUTOMATION FRAMEWORK により Mind Map: AUTOMATION FRAMEWORK

1. ENGINEERING PRODUCTIVITY

1.1. Robust

1.2. Stable

1.3. Performant

1.4. CUSTOMER SUCCESS

1.4.1. Feature Teams

1.4.2. Customer Customer

1.5. Intuitive

1.6. Fun

1.7. How

1.7.1. Efficacy / Metrics

1.7.2. Do it Well

1.7.3. Collaboration

1.7.4. Move Fast - Don't Rush

2. Big Problems Are Managed Not Solved.

3. Code Quality

3.1. Take Care

3.2. Fix

3.3. Maintain

3.4. Anyone Can Write Code that a Computer Understands

4. API First?

5. Moving Forward

5.1. The Future

5.1.1. RunsWith...

5.1.1.1. RunsWithCommunityTemplateTestSuite

5.1.1.2. RunsWithCommunityTemplateTestSuiteWebDriver

5.1.1.3. Dotless

5.1.1.3.1. A Tool

5.1.1.4. A New Annotation Suite?

5.1.1.5. An Answer

5.1.2. TestIm

5.1.2.1. Steel Threads / E2E UI Tests

5.1.2.2. An Answer

5.1.2.2.1. Perhaps an answer for UI Automation in the Future

5.1.2.3. A Tool

5.1.2.3.1. Definitely one of our tools for ui automation now

5.1.3. Robust, Performant, Untuitive, Fun

5.2. The Past

5.2.1. CTTU

5.2.1.1. BasePicassoSelfService*Test

5.2.1.2. BaseCommunityWebdriverTest

5.2.1.3. CommunityTemplateTestBuilder (testAnnotations)

5.2.1.4. CommunityTemplateSetupBuilder (ftestSetupRequests)

5.2.1.5. Dotless

5.2.1.5.1. A Tool

5.2.2. Fragile

5.2.3. What Other Paradigms?

6. Ownership

7. Various Frameworks / Divergent Code Paths

7.1. LWR, Aura

7.2. LWR Annotation Processor VS RunsWith and CTTU Annotation Processor