Hi,
we had a Go to meeting today with a support specialist for the test list issue, where it was not running if the list had more than 4 test cases. Our project size is 700 MB ( with different modules with in the same project ). and will grow more as we complete more module automations.
Support specialist looked into the issue and suggested few options.
1. Upgrade the RAM size from existing 4 GB to 8 GB
- Wanted to ensure before we invest on this , that the test list will indeed work with this configuration. Is this tested and is this the minimum requirement to run the test list when the project size is more ?
2. Split the Project into smaller ones , 1 project per module.
- Is this possible , where we have integration scenarios / regression scenarios where we refer the process/elements accros different modules ?
Pls help , as we are in tough situation , where we have 500 scripts automated and we cannot afford to have QAs to run individual tests for weeks, and we are anticipating that we are going to have another 1000 scripts automated.
we had a Go to meeting today with a support specialist for the test list issue, where it was not running if the list had more than 4 test cases. Our project size is 700 MB ( with different modules with in the same project ). and will grow more as we complete more module automations.
Support specialist looked into the issue and suggested few options.
1. Upgrade the RAM size from existing 4 GB to 8 GB
- Wanted to ensure before we invest on this , that the test list will indeed work with this configuration. Is this tested and is this the minimum requirement to run the test list when the project size is more ?
2. Split the Project into smaller ones , 1 project per module.
- Is this possible , where we have integration scenarios / regression scenarios where we refer the process/elements accros different modules ?
Pls help , as we are in tough situation , where we have 500 scripts automated and we cannot afford to have QAs to run individual tests for weeks, and we are anticipating that we are going to have another 1000 scripts automated.
4 Answers, 1 is accepted
0
Girish
Top achievements
Rank 1
Rank 1
answered on 12 Sep 2013, 08:03 AM
Can some one pls share their experience?
0
Hi Girish,
Boyan Boev
Telerik
My colleague Ivaylo will continue the discussion in ticket 732891.
Thank you.
Boyan Boev
Telerik
0
Bob
Top achievements
Rank 1
Rank 1
answered on 12 Sep 2013, 04:42 PM
Running almost 500 tests on 4GB of RAM in one of my test suites. One of the modules is a admin panel which adjusts the other, a store. Some tests only run in admin, some only in store, others in both. Using NTFS Junctions I was able to split my test suite into three parts without changing the file structure, locations, or names. Here's an abstraction of my folder structure.
Master Folder Structure (C:\TestSuites\Master\)
1 - Admin Tests (Test creating stuff)
2 - Store Tests (Test shopping stuff)
3 - Combined Tests (Test changing settings in the admin side, verifying on the store side)
4 - Admin Steps
5 - Store Steps
6 - Combined Steps
7 - Library (Common to all test suites)
Using junctions, these directories get mapped out so that I have three test suites.
Admin Test Suite (C:\TestSuites\Admin\)
1 - Admin tests (NTFS Junction means this DIR is both "C:\TestSuites\Master\1 - Admin Tests\" & "C:\TestSuites\Admin\1 - Admin Tests\")
4 - Admin Steps
6 - Common Steps
7 - Library
Store Test Suite (C:\TestSuites\Store\)
2 - Store Tests
5 - Store Steps
6 - Common Steps
7 - Library
Combined Test Suite (C:\TestSuites\Combined\)
3 - Combined Tests
4 - Admin Steps
5 - Store Steps
6 - Common Steps
7 - Library
Also, I'd consider ways you can reduce the size of your test suite. When I started data driving instead of having static tests for certain, common actions on one project, I reduced my test suite size by over 25% at the time of the refactoring (from 180MB to 130MB). 3 Steps to click "X", "Y', and "Z" in a search menu requires almost 3 times the space as click "foo" and local data for each test providing "X" "Y", and "Z".
Master Folder Structure (C:\TestSuites\Master\)
1 - Admin Tests (Test creating stuff)
2 - Store Tests (Test shopping stuff)
3 - Combined Tests (Test changing settings in the admin side, verifying on the store side)
4 - Admin Steps
5 - Store Steps
6 - Combined Steps
7 - Library (Common to all test suites)
Using junctions, these directories get mapped out so that I have three test suites.
Admin Test Suite (C:\TestSuites\Admin\)
1 - Admin tests (NTFS Junction means this DIR is both "C:\TestSuites\Master\1 - Admin Tests\" & "C:\TestSuites\Admin\1 - Admin Tests\")
4 - Admin Steps
6 - Common Steps
7 - Library
Store Test Suite (C:\TestSuites\Store\)
2 - Store Tests
5 - Store Steps
6 - Common Steps
7 - Library
Combined Test Suite (C:\TestSuites\Combined\)
3 - Combined Tests
4 - Admin Steps
5 - Store Steps
6 - Common Steps
7 - Library
Also, I'd consider ways you can reduce the size of your test suite. When I started data driving instead of having static tests for certain, common actions on one project, I reduced my test suite size by over 25% at the time of the refactoring (from 180MB to 130MB). 3 Steps to click "X", "Y', and "Z" in a search menu requires almost 3 times the space as click "foo" and local data for each test providing "X" "Y", and "Z".
0
Hi Robert,
Boyan Boev
Telerik
Thank you for sharing your knowledge and helping other. We really appreciate it.
Thank you!
Boyan Boev
Telerik