Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Software Test Strategies for the RNC RNH Subsystem
KTH, School of Electrical Engineering (EES), Communication Networks.
2013 (English)Independent thesis Advanced level (degree of Master (Two Years)), 20 credits / 30 HE creditsStudent thesis
Abstract [en]

This work concerns software testing strategies for the Radio Network Controller (RNC) RadioNetwork Handler (RNH) subsystem at the WCDMA development department at Ericsson AB. Due to the rapid development in the area of radio communication It is crucial to constantly develop and deliver new software components without errors in the code, which has to be tested and proved to work on a regular basis. Since development teams are working in parallel, one cannot uphold another team for long periods for testing purposes. It should be easy and straightforward to implement and maintain RNH tests. The main goal is to propose the best way of software testing for the RNH subsystem with respect to the agile way of working.

In the first part of this work an investigation of the RNH software was done. This was to define a template for code classification. The aim of the classification is to identify a smallest testable unit for different testing levels. The data classes were considered as smallest testable unit for testing on low level. In the second part, unit test was deployed to two different blocks to evaluate unit testing and prove testability of data classes on a low level. In addition, the automated regression test framework was evaluated with respect to node level testing performance. In the third part, unit test was evaluated in comparison to the current testing level at RNH.

The major result of this investigation shows all testing levels are required for the RNH subsystem, because each level focuses on a specific area of software testing. Furthermore, unit testing is recommended to be a permanent testing level at RNH subsystem, since unit testing is promoted by agile testing strategies (test as early as possible). Besides, when more detailed test on low level (unit testing) is applied, it may lead to the less testing effort on higher level.

Place, publisher, year, edition, pages
2013. , 74 p.
Series
EES Examensarbete / Master Thesis, XR-EE-LCN 2013:003
Keyword [en]
mobile networks, testing
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:kth:diva-116599OAI: oai:DiVA.org:kth-116599DiVA: diva2:597126
External cooperation
Ericsson AB
Educational program
Master of Science - Network Services and Systems
Uppsok
Technology
Supervisors
Examiners
Available from: 2013-01-31 Created: 2013-01-22 Last updated: 2014-02-12Bibliographically approved

Open Access in DiVA

fulltext(2312 kB)397 downloads
File information
File name FULLTEXT01.pdfFile size 2312 kBChecksum SHA-512
0dd6f59ad75e8e9f05132d7c8200a656add38dc592c181d1cc99fad45dc3fc980648f8fc0138e41903bbe57f95c790c7b8e35403ed54e721c8d03e24589b3845
Type fulltextMimetype application/pdf

By organisation
Communication Networks
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar
Total: 397 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 121 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf